[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171219012214.GA19673@codemonkey.org.uk>
Date: Mon, 18 Dec 2017 20:22:14 -0500
From: Dave Jones <davej@...emonkey.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: proc_flush_task oops
On Mon, Dec 18, 2017 at 03:50:52PM -0800, Linus Torvalds wrote:
> On Mon, Dec 18, 2017 at 3:10 PM, Dave Jones <davej@...emonkey.org.uk> wrote:
> > On Mon, Dec 18, 2017 at 10:15:41PM +0000, Al Viro wrote:
> > > On Mon, Dec 18, 2017 at 04:44:38PM -0500, Dave Jones wrote:
> > > > I've hit this twice today. It's odd, because afaics, none of this code
> > > > has really changed in a long time.
> > >
> > > Which tree had that been?
> >
> > Linus, rc4.
>
> Ok, so the original report was marked as spam for me for whatever
> reason. I ended up re-analyzing the oops, but came to the same
> conclusion you did: it's a NULL mnt pointer in proc_flush_task_mnt().
> ..
> But I don't see what would have changed in this area recently.
>
> Do you end up saving the seeds that cause crashes? Is this
> reproducible? (Other than seeing it twoce, of course)
Hit it another two times in the last hour, so it's pretty reproducable.
Running it now with some more logging, will see if that yields any extra clues.
Dave
Powered by blists - more mailing lists