From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Nathan Scott" <nathans@sgi.com>
Cc: xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
LKML <linux-kernel@vger.kernel.org>,
"Arjan van de Ven" <arjan@linux.intel.com>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: 2.6.18-rc4+ext4 oops while mounting xfs
Date: Fri, 11 Aug 2006 01:46:08 +0200 [thread overview]
Message-ID: <6bffcb0e0608101646k4f412e7ave59bc20a038f51fe@mail.gmail.com> (raw)
In-Reply-To: <20060811091659.E2596458@wobbly.melbourne.sgi.com>
Hi Nathan,
On 11/08/06, Nathan Scott <nathans@sgi.com> wrote:
> On Fri, Aug 11, 2006 at 01:08:44AM +0200, Michal Piotrowski wrote:
> > On 10/08/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> > > ...
> > > Aug 10 16:50:53 ltg01-fedora kernel: EFLAGS: 00010002 (2.6.18-rc4 #119)
> > > Aug 10 16:50:53 ltg01-fedora kernel: EIP is at __lock_acquire+0x2ca/0x9b6
> > > Aug 10 16:50:53 ltg01-fedora kernel: Call Trace:
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c0135ccb>]
> > > lock_release_non_nested+0xc5/0x11d
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c0136026>] lock_release+0x12f/0x159
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c02d579e>]
> > > __mutex_unlock_slowpath+0x99/0xff
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c02d580c>] mutex_unlock+0x8/0xa
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c016d3b2>]
> > > generic_shutdown_super+0xbb/0x113
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c016d42a>] kill_block_super+0x20/0x32
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c016d4ea>] deactivate_super+0x5d/0x6f
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c0180336>] mntput_no_expire+0x42/0x72
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c0173147>]
> > > path_release_on_umount+0x15/0x18
> > > Aug 10 16:50:53 ltg01-fedora kernel: [<c018147c>] sys_umount+0x1e7/0x21b
> > ...
> > It's fixed in latest 2.6.18-rc4-git*.
>
> We've not changed anything mount related in current git* kernels,
> are you sure its fixed (did it happen every time)? I'm not sure
> how its XFS related too ... looks possibly lockdep related (from
> *non_nested back there?)
You are absolutely right. Oops appears only with CONFIG_DEBUG_LOCKDEP enabled.
> and perhaps an issue with sb->s_lock in
> the kill_block_super unlock_super call?
>
> cheers.
>
> --
> Nathan
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
prev parent reply other threads:[~2006-08-10 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 15:05 Michal Piotrowski
2006-08-10 23:08 ` Michal Piotrowski
2006-08-10 23:16 ` Nathan Scott
2006-08-10 23:46 ` Michal Piotrowski [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=6bffcb0e0608101646k4f412e7ave59bc20a038f51fe@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nathans@sgi.com \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.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
all inboxes | Powered by JetHome®