From: "François Figarola" <francois.figarola@i-consult.fr>
To: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
Cc: hch@infradead.org,
device-mapper development <dm-devel@redhat.com>,
linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-raid@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [dm-devel] [BUG] kernel 2.6.32.x hangs during boot process
Date: Fri, 29 Jan 2010 08:06:29 +0100 [thread overview]
Message-ID: <4B6288F5.7060508@i-consult.fr> (raw)
In-Reply-To: <4B612F89.7020503@ce.jp.nec.com>
Jun'ichi Nomura a écrit :
>>> On Sat, 16 Jan 2010 10:58:30 +0100
>>> Fran__ois Figarola <francois.figarola@i-consult.fr> wrote:
>>>
>>>> Since I've tried to boot 2.6.32.x kernel, my system hangs during the
>>>> boot process, and I think it could be related to the problem reported
>>>> earlier by Megastorage (http://lkml.org/lkml/2010/1/10/92).
>>>>
>>>> The hardware is a Dell PowerEdge 2950 which runs fine with the
>>>> 2.6.31.x kernel series (actually running with the latest 2.6.31.11),
>>>> and the system is debian etch.
>>>>
>>>> Here is the trace of the bug I've got (using netconsole) with a
>>>> 2.6.32.3 kernel :
>>>>
>>>> BUG: Dentry ffff880667690000{i=41a46,n=sleep} still in use (8)
>>>> [unmount of ext3 dm-4]
>>>> ------------[ cut here ]------------
>>>> kernel BUG at fs/dcache.c:670!
>>>>
>
> I can reproduce this when suspend/resume read-only mounted dm device.
>
> When MS_RDONLY, both freeze_bdev and thaw_bdev call deactivate_locked_super,
> which seems wrong. The change was introduced with the commit below:
>
> commit 4504230a71566785a05d3e6b53fa1ee071b864eb
> Author: Christoph Hellwig <hch@lst.de>
> Date: Mon Aug 3 23:28:35 2009 +0200
>
> freeze_bdev: grab active reference to frozen superblocks
>
> With the attached patch, both remount-ro and remount-rw are
> rejected as EBUSY on freezed device as expected.
>
> Christoph, do you think this is the right fix?
>
>
With the fix from Jun'ichi Nomura, a 2.6.32.5 kernel
boots now correctly.
Thanks.
prev parent reply other threads:[~2010-01-29 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 9:58 [BUG] kernel 2.6.32.x hangs during boot process François Figarola
2010-01-23 0:07 ` Andrew Morton
2010-01-28 2:42 ` Neil Brown
2010-01-28 6:32 ` [dm-devel] " Jun'ichi Nomura
2010-01-28 18:16 ` Thomas Backlund
2010-01-28 18:25 ` Christoph Hellwig
2010-01-29 0:56 ` [BUGFIX] [PATCH] freeze_bdev: don't deactivate successfully frozen MS_RDONLY sb Jun'ichi Nomura
2010-01-30 18:44 ` Thomas Backlund
2010-01-29 7:06 ` François Figarola [this message]
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=4B6288F5.7060508@i-consult.fr \
--to=francois.figarola@i-consult.fr \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).