[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091217090250.GA4844@elte.hu>
Date: Thu, 17 Dec 2009 10:02:50 +0100
From: Ingo Molnar <mingo@...e.hu>
To: linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Christoph Hellwig <hch@....de>
Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Andrew Morton <akpm@...ux-foundation.org>,
Dave Chinner <david@...morbit.com>,
Badari Pulavarty <pbadari@...ibm.com>,
Jeff Moyer <jmoyer@...hat.com>,
Jens Axboe <jens.axboe@...cle.com>,
Zach Brown <zach.brown@...cle.com>,
Al Viro <viro@...iv.linux.org.uk>, Alex Elder <aelder@....com>,
Mark Fasheh <mfasheh@...e.com>,
Joel Becker <joel.becker@...cle.com>
Subject: -tip: origin tree boot crash
Today's -tip crashes during bootup on one of my testsystems, and i've bisected
it back to this commit:
| 5fe878ae7f82fbf0830dbfaee4c5ca18f3aee442 is the first bad commit
| commit 5fe878ae7f82fbf0830dbfaee4c5ca18f3aee442
| Author: Christoph Hellwig <hch@....de>
| Date: Tue Dec 15 16:47:50 2009 -0800
|
| direct-io: cleanup blockdev_direct_IO locking
|
| Currently the locking in blockdev_direct_IO is a mess, we have three
| different locking types and very confusing checks for some of them. The
| most complicated one is DIO_OWN_LOCKING for reads, which happens to not
| actually be used.
I have no bootlog available currently. The kernel config is attached.
I've reverted the patch from -tip for now.
Ingo
View attachment "config" of type "text/plain" (76467 bytes)
Powered by blists - more mailing lists