Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932147AbWHJTHF@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932147AbWHJTHF (ORCPT <rfc822;willy@w.ods.org>);
	Thu, 10 Aug 2006 15:07:05 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932340AbWHJTHE
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 10 Aug 2006 15:07:04 -0400
Received: from bayc1-pasmtp04.bayc1.hotmail.com ([65.54.191.164]:63626 "EHLO
	BAYC1-PASMTP04.bayc1.hotmail.com") by vger.kernel.org with ESMTP
	id S932147AbWHJTHC (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 10 Aug 2006 15:07:02 -0400
Message-ID: <BAYC1-PASMTP0447FD63244C3ED669CA2FB94A0@CEZ.ICE>
X-Originating-IP: [65.92.42.161]
X-Originating-Email: [johnmccuthan@sympatico.ca]
Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2
From: John McCutchan <john@johnmccutchan.com>
Reply-To: john@johnmccutchan.com
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: cmm@us.ibm.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
       ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org,
       John McCutchan <ttb@tentacle.dhs.org>, Robert Love <rml@novell.com>
In-Reply-To: <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com>
References: <1155172597.3161.72.camel@localhost.localdomain>
	 <6bffcb0e0608100702m1ad3925bw3e5f0e4804210fc9@mail.gmail.com>
	 <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Thu, 10 Aug 2006 15:06:41 -0400
Message-Id: <1155236801.3162.1.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.2 
X-OriginalArrivalTime: 10 Aug 2006 19:07:01.0315 (UTC) FILETIME=[28E74930:01C6BCB0]
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2282
Lines: 57

On Thu, 2006-10-08 at 17:15 +0200, Michal Piotrowski wrote:
> On 10/08/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> > Hi,
> >
> > On 10/08/06, Mingming Cao <cmm@us.ibm.com> wrote:
> > > This series of patch forkes a new filesystem, ext4, from the current
> > > ext3 filesystem, as the code base to work on, for the big features such
> > > as extents and larger fs(48 bit blk number) support, per our discussion
> > > on lkml a few weeks ago.
> >
> > It appears after a few minutes of running
> >
> > #! /bin/bash
> > while true
> > do
> > sudo mount -o loop -t ext3dev /home/fs-farm/ext4.img /mnt/fs-farm/ext4/
> > sudo umount /mnt/fs-farm/ext4/
> > done
> >
> > BUG: warning at /usr/src/linux-work2/fs/inotify.c:171/set_dentry_child_flags()
> >  [<c0104006>] show_trace_log_lvl+0x58/0x152
> >  [<c01046ad>] show_trace+0xd/0x10
> >  [<c0104775>] dump_stack+0x19/0x1b
> >  [<c018aa7f>] set_dentry_child_flags+0x5a/0x119
> >  [<c018ab94>] remove_watch_no_event+0x56/0x64
> >  [<c018ac62>] inotify_remove_watch_locked+0x12/0x34
> >  [<c018af1b>] inotify_rm_wd+0x75/0x93
> >  [<c018b468>] sys_inotify_rm_watch+0x40/0x58
> >  [<c0102f15>] sysenter_past_esp+0x56/0x8d
> > DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
> > Leftover inexact backtrace:
> >  [<c01046ad>] show_trace+0xd/0x10
> >  [<c0104775>] dump_stack+0x19/0x1b
> >  [<c018aa7f>] set_dentry_child_flags+0x5a/0x119
> >  [<c018ab94>] remove_watch_no_event+0x56/0x64
> >  [<c018ac62>] inotify_remove_watch_locked+0x12/0x34
> >  [<c018af1b>] inotify_rm_wd+0x75/0x93
> >  [<c018b468>] sys_inotify_rm_watch+0x40/0x58
> >  [<c0102f15>] sysenter_past_esp+0x56/0x8d
> > kjournald2 starting.  Commit interval 5 seconds
> 
> Definitely it's an inotify bug. I have checked this with other file systems.


I'm going on vacation today, so I won't be able to look at it for a
while. Right off the bat it seems related to Nick Piggin's patch from
February:
inotify-lock-avoidance-with-parent-watch-status-in-dentry.patch.


-- 
John McCutchan <john@johnmccutchan.com>
-
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/