linux-kernel - Re: [PATCH v1] drm/scheduler: Don't kill jobs in interrupt context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <73fde0e0-11d2-a627-0bf9-84ee7d3b5fcc@collabora.com>
Date:   Thu, 14 Jul 2022 17:23:35 +0300
From:   Dmitry Osipenko <dmitry.osipenko@...labora.com>
To:     Andrey Grodzovsky <andrey.grodzovsky@....com>,
        Alex Deucher <alexdeucher@...il.com>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
Cc:     Erico Nunes <nunes.erico@...il.com>,
        Steven Price <steven.price@....com>,
        Tomeu Vizoso <tomeu.vizoso@...labora.com>,
        David Airlie <airlied@...ux.ie>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Alyssa Rosenzweig <alyssa.rosenzweig@...labora.com>,
        Dmitry Osipenko <digetx@...il.com>
Subject: Re: [PATCH v1] drm/scheduler: Don't kill jobs in interrupt context

On 7/14/22 17:14, Andrey Grodzovsky wrote:
> 
> On 2022-07-14 05:57, Dmitry Osipenko wrote:
>> On 7/12/22 11:56, Dmitry Osipenko wrote:
>>> On 7/6/22 18:46, Alex Deucher wrote:
>>>> On Wed, Jul 6, 2022 at 9:49 AM Andrey Grodzovsky
>>>> <andrey.grodzovsky@....com> wrote:
>>>>> On 2022-07-06 03:07, Dmitry Osipenko wrote:
>>>>>
>>>>>> Hello Andrey,
>>>>>>
>>>>>> On 5/17/22 17:48, Dmitry Osipenko wrote:
>>>>>>> On 5/17/22 17:13, Andrey Grodzovsky wrote:
>>>>>>>> Done.
>>>>>>>>
>>>>>>>> Andrey
>>>>>>> Awesome, thank you!
>>>>>>>
>>>>>> Given that this drm-scheduler issue needs to be fixed in the
>>>>>> 5.19-RC and
>>>>>> earlier, shouldn't it be in the drm-fixes and not in drm-next?
>>>>>
>>>>> I pushed it into drm-misc from where it got into drm-next. I don't
>>>>> have
>>>>> permission for drm-fixes.
>>>> The -fixes branch of drm-misc.
>>> Now I don't see the scheduler bugfix neither in the -fixes branch nor in
>>> the -next and today Dave sent out 5.19-rc7 pull request without the
>>> scheduler fix. Could anyone please check what is going on with the DRM
>>> patches? Thanks!
>>>
>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffreedesktop%2Fdrm-misc%2Fcommits%2Fdrm-misc-fixes&amp;data=05%7C01%7Candrey.grodzovsky%40amd.com%7C68b627b8482a4fd28a5608da657f4375%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933894551324163%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=CDdLG%2F7SqCudEnjhBSsXqq15mfhlHlS3xAdAfB%2Bh%2F1s%3D&amp;reserved=0
>>>
>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcgit.freedesktop.org%2Fdrm%2Fdrm-misc%2Flog%2F%3Fh%3Ddrm-misc-fixes&amp;data=05%7C01%7Candrey.grodzovsky%40amd.com%7C68b627b8482a4fd28a5608da657f4375%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933894551324163%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=4Vz40j6F%2FzHYckXEyPEunj9DRSoTXikhNxZDXeocTss%3D&amp;reserved=0
>>>
>> The patch is in the drm-misc-next-fixes, so it wasn't moved to the
>> drm-misc-fixes.
>>
>> Andrey, don't you have access to drm-misc-fixes? Or you meant
>> drm-fixes=drm-misc-fixes?
> 
> 
> I have only accesses to drm-misc-next to which I pushed this patch.

Thank you for the clarification. IIUC, the drm-misc-next-fixes should
become drm-misc-fixes, but perhaps it was late for the 5.19-rc6 for this
patch.

-- 
Best regards,
Dmitry