Re: [PATCH v3 01/24] sched: Fix cpuset_mutex double unlock in __sched_setscheduler()

[Mathieu Desnoyers <mathieu.desnoyers@efficios.com>]

On 2026-11-05 14:54, Mathieu Desnoyers wrote:
> On 2026-11-05 14:51, Kayra Cizmeci wrote:
>> On Thu, Nov 05, 2026 at 02:33:36PM -0500, Mathieu Desnoyers wrote:
>>> From: Andrea Parri <parri.andrea@gmail.com>
>>
>>> Fixes: 111cd11bbc54 ("sched/cpuset: Bring back cpuset_mutex")
>>> Reported-by: Sashiko <sashiko-bot@kernel.org>
>>> Link: https://sashiko.dev/#/patchset/20261016062629.2102883-1- 
>>> sh_def%40163.com
>>> Signed-off-by: Andrea Parri <parri.andrea@gmail.com>
>>> Cc: stable@vger.kernel.org
>>> Reviewed-by: Waiman Long <longman@redhat.com>
>>> Reviewed-by: Kayra Cizmeci <kayracizmeci@gmail.com>
>>> Reviewed-by: Juri Lelli <juri.lelli@redhat.com>
>>
>> You gotta add your own SoB, no?
> I'm just relaying the patch and did not touch it, I'm really unsure.
> In any case it can be picked up by the maintainers through their
> preferred route.
> 
> What's the process for this scenario ?
> 
After review of the DCO documentation, I indeed should have added
my SoB in this case:

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

Thanks for the heads up!

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com