linux-kernel - Re: [patch 02/52] fs: fix superblock iteration race

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: <201006292138.40293.chris2553@googlemail.com>
Date:	Tue, 29 Jun 2010 21:38:40 +0100
From:	Chris Clayton <chris2553@...glemail.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Christoph Hellwig <hch@...radead.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	John Stultz <johnstul@...ibm.com>,
	Frank Mayhar <fmayhar@...gle.com>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [patch 02/52] fs: fix superblock iteration race

On Tuesday 29 June 2010, Nick Piggin wrote:
> On Tue, Jun 29, 2010 at 09:04:33PM +0100, Chris Clayton wrote:
> > On Tuesday 29 June 2010, Linus Torvalds wrote:
> > > On Tue, Jun 29, 2010 at 10:52 AM, Linus Torvalds
> > >
> > > <torvalds@...ux-foundation.org> wrote:
> > > > Look for "2.6.35-rc3 oops trying to suspend" on lkml, for example. No
> > > > guarantee that it's the same thing, but it's "iterate_supers()"
> > > > getting an oops [..]
> > >
> > > Also, "Oops during closedown with 2.6.35-rc3-git3" is an
> > > iterate_supers oops (in the jpg) and Chris says it's repeatable for
> > > him.
> > >
> > > Chris - you could try testing current -git now that I've merged Nick's
> > > patch. It's commit 57439f878af ("fs: fix superblock iteration race"),
> > > and I just pushed it out (so it might take a few minutes to mirror out
> > > to the public git trees, but it should be there shortly).
> >
> > Well, it was repeatable this morning, but despite 30+ shutdowns this
> > evening, I haven't had a single oops. Perhaps I'm just not doing enough
> > computing stuff between startup and shutdown to create the conditions
> > under which I got the oopses this morning. Moreover, I've been using this
> > kernel every day with, maybe two or three shutdowns a day, for two weeks
> > or so now (since just after Linus went on vacation) with no oopses. (The
> > kernel is -rc3 + John Fastabend's "net: fix deliver_no_wcard regression
> > on loopback device" patch).
> >
> > I'll spend a couple of hours doing stuff and see if I can generate an
> > oops. Trouble is, of course, that when I pull and build the latest and
> > greatest, I won't know why I'm not getting oopses, assuming I don't.
>
> Don't worry too much if you can't reproduce. I'd say it is likely to be
> this bug, and if so, it is going to depend significantly on timing and
> ordering of mounts/umounts.

Yes, that makes sense. I did quite a bit of copying files to and from USB 
storage devices this morning. I've got some more to do, so I'll see what that 
produces.

-- 
The more I see, the more I know. The more I know, the less I understand. 
Changing Man - Paul Weller
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/