From: Michal Hocko <mhocko@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Nikolay Borisov <nborisov@suse.com>,
linux-kernel@vger.kernel.org, vbabka.lkml@gmail.com,
linux-mm@kvack.org, mingo@redhat.com
Subject: Re: [PATCH v3] lockdep: Teach lockdep about memalloc_noio_save
Date: Wed, 1 Mar 2017 17:18:54 +0100 [thread overview]
Message-ID: <20170301161854.GJ11730@dhcp22.suse.cz> (raw)
In-Reply-To: <20170301161220.GP6515@twins.programming.kicks-ass.net>
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...
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-03-01 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 11:29 [PATCH v3] lockdep: Teach lockdep about memalloc_noio_save Nikolay Borisov
2017-03-01 12:09 ` Michal Hocko
2017-03-01 15:46 ` Peter Zijlstra
2017-03-01 16:01 ` Peter Zijlstra
2017-03-01 16:05 ` Michal Hocko
2017-03-01 16:12 ` Peter Zijlstra
2017-03-01 16:18 ` Michal Hocko [this message]
2017-03-03 8:04 ` Michal Hocko
2017-03-03 8:22 ` Peter Zijlstra
2017-03-03 8:31 ` Michal Hocko
2017-03-03 8:37 ` Michal Hocko
2017-03-03 8:50 ` Peter Zijlstra
2017-03-03 6:50 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170301161854.GJ11730@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=nborisov@suse.com \
--cc=peterz@infradead.org \
--cc=vbabka.lkml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox