From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Jens Axboe <jaxboe@fusionio.com>,
Christoph Hellwig <hch@infradead.org>,
Michael Guntsche <mike@it-loops.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.39 Block layer regression was [Bug] Boot hangs with 2.6.39-rc[123]]
Date: Thu, 21 Apr 2011 10:59:39 -0700 [thread overview]
Message-ID: <BANLkTim7SLt6TMqJQw35=tnACax0mE1URA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1104211051490.18728@trent.utfs.org>
On Thu, Apr 21, 2011 at 10:53 AM, Christian Kujau <lists@nerdbynature.de> wrote:
> On Fri, 15 Apr 2011 at 08:13, Jens Axboe wrote:
>> I think we are done, Neil just needs to rebase around the current
>> for-linus and then we should expedite things in.
>
> Whatever this was: has it been pushed to Linus yet? I'm on 2.6.39-rc4+
> (from yesterday) and I too experience a hang during boot (and other
> strange things with udev[0])
As of right now, all _known_ block bugs should be fixed in the stuff I
just pushed out, with the current top-of-tree being the merge of the
IDE CD endless loop issue and the NULL ptr oops at elevator change
time:
Merge branch 'for-linus' of git://git.kernel.dk/linux-2.6-block
* 'for-linus' of git://git.kernel.dk/linux-2.6-block:
ide: unexport DISK_EVENT_MEDIA_CHANGE for ide-gd and ide-cd
block: don't propagate unlisted DISK_EVENTs to userland
elevator: check for ELEVATOR_INSERT_SORT_MERGE in !elvpriv case too
but maybe yours is something else.
That said, that udevd message of yours would imply a full root
filesystem, which can cause any amount of issues at boot time..
Linus
next prev parent reply other threads:[~2011-04-21 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 2:06 Michael Guntsche
2011-04-15 3:25 ` Linus Torvalds
2011-04-15 4:22 ` Christoph Hellwig
2011-04-15 6:13 ` Jens Axboe
2011-04-21 17:53 ` Christian Kujau
2011-04-21 17:59 ` Linus Torvalds [this message]
2011-04-21 18:30 ` Christian Kujau
2011-04-21 18:36 ` Jens Axboe
2011-04-21 20:53 ` Christian Kujau
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='BANLkTim7SLt6TMqJQw35=tnACax0mE1URA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mike@it-loops.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
Powered by JetHome