<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body bgcolor="white" lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> [AMD Official Use Only - Internal Distribution Only]<o:p></o:p> <o:p> </o:p> Hi Andrey,<o:p></o:p> Thanks very much.<o:p></o:p> <o:p> </o:p> Best wishes<o:p></o:p> Emily Deng<o:p></o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Grodzovsky, Andrey <Andrey.Grodzovsky@amd.com> Sent: Tuesday, December 3, 2019 12:33 PM To: Deucher, Alexander <Alexander.Deucher@amd.com>; Deng, Emily <Emily.Deng@amd.com> Cc: dri-devel@lists.freedesktop.org; amd-gfx@lists.freedesktop.org; Koenig, Christian <Christian.Koenig@amd.com>; steven.price@arm.com Subject: Re: [PATCH v4] drm/scheduler: Avoid accessing freed bad job.<o:p></o:p> </div> </div> <o:p> </o:p> Turns out Steven's patch was already in so i just cherry-picked the change from drm-next-misc<o:p></o:p> <o:p> </o:p> Emily - it's in.<o:p></o:p> <o:p> </o:p> Andrey<o:p></o:p> <o:p> </o:p> <div> On 12/3/19 2:59 PM, Deucher, Alexander wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> [AMD Official Use Only - Internal Distribution Only]<o:p></o:p> <o:p> </o:p> <div> <div> Cherry pick whatever dependencies you need or pick the older version of the patch. Either way works.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Alex<o:p></o:p> </div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="98%" align="center"> </div> <div id="divRplyFwdMsg"> From: Grodzovsky, Andrey <a href="mailto:Andrey.Grodzovsky@amd.com"> <Andrey.Grodzovsky@amd.com></a> Sent: Tuesday, December 3, 2019 2:57 PM To: Deucher, Alexander <a href="mailto:Alexander.Deucher@amd.com"><Alexander.Deucher@amd.com></a>; Deng, Emily <a href="mailto:Emily.Deng@amd.com"><Emily.Deng@amd.com></a> Cc: <a href="mailto:dri-devel@lists.freedesktop.org">dri-devel@lists.freedesktop.org</a> <a href="mailto:dri-devel@lists.freedesktop.org"><dri-devel@lists.freedesktop.org></a>; <a href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a> <a href="mailto:amd-gfx@lists.freedesktop.org"> <amd-gfx@lists.freedesktop.org></a>; Koenig, Christian <a href="mailto:Christian.Koenig@amd.com"> <Christian.Koenig@amd.com></a>; <a href="mailto:steven.price@arm.com">steven.price@arm.com</a> <a href="mailto:steven.price@arm.com"><steven.price@arm.com></a> Subject: Re: [PATCH v4] drm/scheduler: Avoid accessing freed bad job. <o:p> </o:p> <div> <o:p></o:p> </div> </div> <div> I don't think i can apply this patch 'as is' as this has dependency on patch by Steven which also wasn't applied yet - 588b982 Steven Price 6 weeks ago drm: Don't free jobs in wait_event_interruptible()<o:p></o:p> <o:p> </o:p> Andrey<o:p></o:p> <o:p> </o:p> <div> On 12/3/19 2:44 PM, Deucher, Alexander wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> [AMD Official Use Only - Internal Distribution Only]<o:p></o:p> <o:p> </o:p> <div> <div> Please go ahead an apply whatever version is necessary for amd-staging-drm-next.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Alex<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div class="MsoNormal" align="center" style="text-align:center;background:white"> <hr size="2" width="98%" align="center"> </div> <div id="x_divRplyFwdMsg"> From: Grodzovsky, Andrey <a href="mailto:Andrey.Grodzovsky@amd.com"> <Andrey.Grodzovsky@amd.com></a> Sent: Tuesday, December 3, 2019 2:10 PM To: Deng, Emily <a href="mailto:Emily.Deng@amd.com"><Emily.Deng@amd.com></a>; Deucher, Alexander <a href="mailto:Alexander.Deucher@amd.com"><Alexander.Deucher@amd.com></a> Cc: <a href="mailto:dri-devel@lists.freedesktop.org">dri-devel@lists.freedesktop.org</a> <a href="mailto:dri-devel@lists.freedesktop.org"><dri-devel@lists.freedesktop.org></a>; <a href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a> <a href="mailto:amd-gfx@lists.freedesktop.org"> <amd-gfx@lists.freedesktop.org></a>; Koenig, Christian <a href="mailto:Christian.Koenig@amd.com"> <Christian.Koenig@amd.com></a>; <a href="mailto:steven.price@arm.com">steven.price@arm.com</a> <a href="mailto:steven.price@arm.com"><steven.price@arm.com></a> Subject: Re: [PATCH v4] drm/scheduler: Avoid accessing freed bad job. <o:p> </o:p> <div> <o:p></o:p> </div> </div> <div> <div> Yes - Christian just pushed it to drm-next-misc - I guess Alex/Christian didn't pull to amd-staging-drm-next yet. Andrey On 12/2/19 2:24 PM, Deng, Emily wrote: > [AMD Official Use Only - Internal Distribution Only] > > Hi Andrey, > Seems this patch is still not in amd-staging-drm-next? > > Best wishes > Emily Deng > > > >> -----Original Message----- >> From: Deng, Emily >> Sent: Tuesday, November 26, 2019 4:41 PM >> To: Grodzovsky, Andrey <a href="mailto:Andrey.Grodzovsky@amd.com"><Andrey.Grodzovsky@amd.com></a> >> Cc: <a href="mailto:dri-devel@lists.freedesktop.org">dri-devel@lists.freedesktop.org</a>; <a href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a>; Koenig, >> Christian <a href="mailto:Christian.Koenig@amd.com"><Christian.Koenig@amd.com></a>; <a href="mailto:steven.price@arm.com">steven.price@arm.com</a> >> Subject: RE: [PATCH v4] drm/scheduler: Avoid accessing freed bad job. >> >> [AMD Official Use Only - Internal Distribution Only] >> >> Reviewed-by: Emily Deng <a href="mailto:Emily.Deng@amd.com"><Emily.Deng@amd.com></a> >> >>> -----Original Message----- >>> From: Grodzovsky, Andrey <a href="mailto:Andrey.Grodzovsky@amd.com"><Andrey.Grodzovsky@amd.com></a> >>> Sent: Tuesday, November 26, 2019 7:37 AM >>> Cc: <a href="mailto:dri-devel@lists.freedesktop.org">dri-devel@lists.freedesktop.org</a>; <a href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a>; >>> Koenig, Christian <a href="mailto:Christian.Koenig@amd.com"><Christian.Koenig@amd.com></a>; Deng, Emily >>> <a href="mailto:Emily.Deng@amd.com"><Emily.Deng@amd.com></a>; <a href="mailto:steven.price@arm.com"> steven.price@arm.com</a> >>> Subject: Re: [PATCH v4] drm/scheduler: Avoid accessing freed bad job. >>> >>> Ping >>> >>> Andrey >>> >>> On 11/25/19 3:51 PM, Andrey Grodzovsky wrote: >>>> Problem: >>>> Due to a race between drm_sched_cleanup_jobs in sched thread and >>>> drm_sched_job_timedout in timeout work there is a possiblity that bad >>>> job was already freed while still being accessed from the timeout >>>> thread. >>>> >>>> Fix: >>>> Instead of just peeking at the bad job in the mirror list remove it >>>> from the list under lock and then put it back later when we are >>>> garanteed no race with main sched thread is possible which is after >>>> the thread is parked. >>>> >>>> v2: Lock around processing ring_mirror_list in drm_sched_cleanup_jobs. >>>> >>>> v3: Rebase on top of drm-misc-next. v2 is not needed anymore as >>>> drm_sched_get_cleanup_job already has a lock there. >>>> >>>> v4: Fix comments to relfect latest code in drm-misc. >>>> >>>> Signed-off-by: Andrey Grodzovsky <a href="mailto:andrey.grodzovsky@amd.com"> <andrey.grodzovsky@amd.com></a> >>>> Reviewed-by: Christian K�nig <a href="mailto:christian.koenig@amd.com"><christian.koenig@amd.com></a> >>>> Tested-by: Emily Deng <a href="mailto:Emily.Deng@amd.com"><Emily.Deng@amd.com></a> >>>> --- >>>> drivers/gpu/drm/scheduler/sched_main.c | 27 >>> +++++++++++++++++++++++++++ >>>> 1 file changed, 27 insertions(+) >>>> >>>> diff --git a/drivers/gpu/drm/scheduler/sched_main.c >>>> b/drivers/gpu/drm/scheduler/sched_main.c >>>> index 6774955..1bf9c40 100644 >>>> --- a/drivers/gpu/drm/scheduler/sched_main.c >>>> +++ b/drivers/gpu/drm/scheduler/sched_main.c >>>> @@ -284,10 +284,21 @@ static void drm_sched_job_timedout(struct >>> work_struct *work) >>>> unsigned long flags; >>>> >>>> sched = container_of(work, struct drm_gpu_scheduler, >>>> work_tdr.work); >>>> + >>>> + /* Protects against concurrent deletion in >>> drm_sched_get_cleanup_job */ >>>> + spin_lock_irqsave(&sched->job_list_lock, flags); >>>> job = list_first_entry_or_null(&sched->ring_mirror_list, >>>> struct drm_sched_job, node); >>>> >>>> if (job) { >>>> + /* >>>> + * Remove the bad job so it cannot be freed by concurrent >>>> + * drm_sched_cleanup_jobs. It will be reinserted back after >>> sched->thread >>>> + * is parked at which point it's safe. >>>> + */ >>>> + list_del_init(&job->node); >>>> + spin_unlock_irqrestore(&sched->job_list_lock, flags); >>>> + >>>> job->sched->ops->timedout_job(job); >>>> >>>> /* >>>> @@ -298,6 +309,8 @@ static void drm_sched_job_timedout(struct >>> work_struct *work) >>>> job->sched->ops->free_job(job); >>>> sched->free_guilty = false; >>>> } >>>> + } else { >>>> + spin_unlock_irqrestore(&sched->job_list_lock, flags); >>>> } >>>> >>>> spin_lock_irqsave(&sched->job_list_lock, flags); @@ -370,6 +383,20 >>>> @@ void drm_sched_stop(struct drm_gpu_scheduler *sched, struct >>> drm_sched_job *bad) >>>> kthread_park(sched->thread); >>>> >>>> /* >>>> + * Reinsert back the bad job here - now it's safe as >>>> + * drm_sched_get_cleanup_job cannot race against us and release the >>>> + * bad job at this point - we parked (waited for) any in progress >>>> + * (earlier) cleanups and drm_sched_get_cleanup_job will not be >>> called >>>> + * now until the scheduler thread is unparked. >>>> + */ >>>> + if (bad && bad->sched == sched) >>>> + /* >>>> + * Add at the head of the queue to reflect it was the earliest >>>> + * job extracted. >>>> + */ >>>> + list_add(&bad->node, &sched->ring_mirror_list); >>>> + >>>> + /* >>>> * Iterate the job list from later to earlier one and either deactive >>>> * their HW callbacks or remove them from mirror list if they already >>>> * signaled.<o:p></o:p> </div> </div> </div> </blockquote> </div> </div> </blockquote> </div> </div> </body> </html>