linux-kernel - Re: [PATCH v3] lockdep: Teach lockdep about memalloc_noio

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: <20170303080419.GA31582@dhcp22.suse.cz>
Date:   Fri, 3 Mar 2017 09:04:20 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Nikolay Borisov <nborisov@...e.com>, linux-kernel@...r.kernel.org,
        vbabka.lkml@...il.com, linux-mm@...ck.org, mingo@...hat.com
Subject: Re: [PATCH v3] lockdep: Teach lockdep about memalloc_noio_save

On Wed 01-03-17 17:18:54, Michal Hocko wrote:
> On Wed 01-03-17 17:12:20, Peter Zijlstra wrote:
> > On Wed, Mar 01, 2017 at 05:05:30PM +0100, Michal Hocko wrote:
> > > Anyway, does the following help?
> > 
> > > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> > > index 47e4f82380e4..d5386ad7ed3f 100644
> > > --- a/kernel/locking/lockdep.c
> > > +++ b/kernel/locking/lockdep.c
> > > @@ -47,6 +47,7 @@
> > >  #include <linux/kmemcheck.h>
> > >  #include <linux/random.h>
> > >  #include <linux/jhash.h>
> > > +#include <linux/sched.h>
> > 
> > No, Ingo moved that to linux/sched/mm.h in tip/master, which was the
> > problem.
> 
> Yeah, have seen your email after I posted mine...
> 
> > But I think this needs to go to Linus in this cycle, right? In which
> > case Ingo gets to sort the fallout.
> 
> Yes I think it would be better to send it sonner rahter than later.
> People also might want to backport it to older kernels...

Would you mind if I took this patch and route it via Andrew? I plan to
resubmit my scope NOFS patchset [1] and [2] will need to be refreshed on
top of it so it would be easier for me that way.

[1] http://lkml.kernel.org/r/20170206140718.16222-1-mhocko@kernel.org
[2] http://lkml.kernel.org/r/20170206140718.16222-4-mhocko@kernel.org
-- 
Michal Hocko
SUSE Labs