linux-kernel - Re: [PATCH 0/2] sched: pick and check task if double_lock

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]

Date:   Thu, 12 Apr 2018 08:20:10 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Li Bin <huawei.libin@...wei.com>, mingo@...hat.com,
        linux-kernel@...r.kernel.org, guohanjun@...wei.com
Subject: Re: [PATCH 0/2] sched: pick and check task if double_lock_balance()
 unlock the rq

On Thu, 12 Apr 2018 14:11:45 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> On Thu, Apr 12, 2018 at 06:58:53PM +0800, Li Bin wrote:
> > Li Bin (1):
> >   sched/deadline.c: pick and check task if double_lock_balance() unlock
> >     the rq
> > 
> > Zhou Chengming (1):
> >   sched/rt.c: pick and check task if double_lock_balance() unlock the
> >     rq
> >   
> 
> Much thanks!
> 
> Acked-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> 
> Ingo, please apply.

You can add my:

Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>

but I would still like to see the declaration of next_task before the
comment, just for style concerns.

-- Steve