Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932290AbWHJXqL@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932290AbWHJXqL (ORCPT <rfc822;willy@w.ods.org>);
	Thu, 10 Aug 2006 19:46:11 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932307AbWHJXqL
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 10 Aug 2006 19:46:11 -0400
Received: from py-out-1112.google.com ([64.233.166.181]:30659 "EHLO
	py-out-1112.google.com") by vger.kernel.org with ESMTP
	id S932290AbWHJXqK (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 10 Aug 2006 19:46:10 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=nZz2o58y26qK0Qh2/qtVAA/QicOoMoo8RGQXoe0jndE5oLarbs7UCtA0zULV+t+putWeQs81mOKDd+oMRHVdn6NUWSRlNrQSp0/CfbpCdShfGEz44M2OT0KIbfLOnvI0E/tgQKE/R4vLqVppEfe45Z3/WaguvcggIgO+/Hxz4O4=
Message-ID: <6bffcb0e0608101646k4f412e7ave59bc20a038f51fe@mail.gmail.com>
Date: Fri, 11 Aug 2006 01:46:08 +0200
From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Nathan Scott" <nathans@sgi.com>
Subject: Re: 2.6.18-rc4+ext4 oops while mounting xfs
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>
In-Reply-To: <20060811091659.E2596458@wobbly.melbourne.sgi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6bffcb0e0608100805k42357f5bxa73189c38fb926df@mail.gmail.com>
	 <6bffcb0e0608101608j4fc41945of65173793703a065@mail.gmail.com>
	 <20060811091659.E2596458@wobbly.melbourne.sgi.com>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2149
Lines: 54

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/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/