From mboxrd@z Thu Jan 1 00:00:00 1970 From: John McCutchan Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2 Date: Thu, 10 Aug 2006 15:06:41 -0400 Message-ID: References: <1155172597.3161.72.camel@localhost.localdomain> <6bffcb0e0608100702m1ad3925bw3e5f0e4804210fc9@mail.gmail.com> <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com> Reply-To: john@johnmccutchan.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit 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 , Robert Love Return-path: 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 ); Thu, 10 Aug 2006 15:07:02 -0400 To: Michal Piotrowski In-Reply-To: <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com> Message-Id: <1155236801.3162.1.camel@localhost.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2006-10-08 at 17:15 +0200, Michal Piotrowski wrote: > On 10/08/06, Michal Piotrowski wrote: > > Hi, > > > > On 10/08/06, Mingming Cao 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() > > [] show_trace_log_lvl+0x58/0x152 > > [] show_trace+0xd/0x10 > > [] dump_stack+0x19/0x1b > > [] set_dentry_child_flags+0x5a/0x119 > > [] remove_watch_no_event+0x56/0x64 > > [] inotify_remove_watch_locked+0x12/0x34 > > [] inotify_rm_wd+0x75/0x93 > > [] sys_inotify_rm_watch+0x40/0x58 > > [] sysenter_past_esp+0x56/0x8d > > DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d > > Leftover inexact backtrace: > > [] show_trace+0xd/0x10 > > [] dump_stack+0x19/0x1b > > [] set_dentry_child_flags+0x5a/0x119 > > [] remove_watch_no_event+0x56/0x64 > > [] inotify_remove_watch_locked+0x12/0x34 > > [] inotify_rm_wd+0x75/0x93 > > [] sys_inotify_rm_watch+0x40/0x58 > > [] 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: John McCutchan Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2 Date: Thu, 10 Aug 2006 15:06:41 -0400 Message-ID: <1155236801.3162.1.camel__19292.5829127946$1155236847$gmane$org@localhost.localdomain> References: <1155172597.3161.72.camel@localhost.localdomain> <6bffcb0e0608100702m1ad3925bw3e5f0e4804210fc9@mail.gmail.com> <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com> Reply-To: john@johnmccutchan.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: akpm@osdl.org, ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, cmm@us.ibm.com, linux-fsdevel@vger.kernel.org, John McCutchan , Robert Love Return-path: To: Michal Piotrowski In-Reply-To: <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com> Message-Id: <1155236801.3162.1.camel@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ext2-devel-bounces@lists.sourceforge.net Errors-To: ext2-devel-bounces@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org On Thu, 2006-10-08 at 17:15 +0200, Michal Piotrowski wrote: > On 10/08/06, Michal Piotrowski wrote: > > Hi, > > > > On 10/08/06, Mingming Cao 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() > > [] show_trace_log_lvl+0x58/0x152 > > [] show_trace+0xd/0x10 > > [] dump_stack+0x19/0x1b > > [] set_dentry_child_flags+0x5a/0x119 > > [] remove_watch_no_event+0x56/0x64 > > [] inotify_remove_watch_locked+0x12/0x34 > > [] inotify_rm_wd+0x75/0x93 > > [] sys_inotify_rm_watch+0x40/0x58 > > [] sysenter_past_esp+0x56/0x8d > > DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d > > Leftover inexact backtrace: > > [] show_trace+0xd/0x10 > > [] dump_stack+0x19/0x1b > > [] set_dentry_child_flags+0x5a/0x119 > > [] remove_watch_no_event+0x56/0x64 > > [] inotify_remove_watch_locked+0x12/0x34 > > [] inotify_rm_wd+0x75/0x93 > > [] sys_inotify_rm_watch+0x40/0x58 > > [] 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 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 From mboxrd@z Thu Jan 1 00:00:00 1970 From: John McCutchan Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2 Date: Thu, 10 Aug 2006 15:06:41 -0400 Message-ID: <1155236801.3162.1.camel__45938.0004358993$1155236887$gmane$org@localhost.localdomain> References: <1155172597.3161.72.camel@localhost.localdomain> <6bffcb0e0608100702m1ad3925bw3e5f0e4804210fc9@mail.gmail.com> <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com> Reply-To: john@johnmccutchan.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit 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 , Robert Love Return-path: To: Michal Piotrowski In-Reply-To: <6bffcb0e0608100815q4b0b35b6mc2799181abd5786e@mail.gmail.com> Message-Id: <1155236801.3162.1.camel@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2006-10-08 at 17:15 +0200, Michal Piotrowski wrote: > On 10/08/06, Michal Piotrowski wrote: > > Hi, > > > > On 10/08/06, Mingming Cao 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() > > [] show_trace_log_lvl+0x58/0x152 > > [] show_trace+0xd/0x10 > > [] dump_stack+0x19/0x1b > > [] set_dentry_child_flags+0x5a/0x119 > > [] remove_watch_no_event+0x56/0x64 > > [] inotify_remove_watch_locked+0x12/0x34 > > [] inotify_rm_wd+0x75/0x93 > > [] sys_inotify_rm_watch+0x40/0x58 > > [] sysenter_past_esp+0x56/0x8d > > DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d > > Leftover inexact backtrace: > > [] show_trace+0xd/0x10 > > [] dump_stack+0x19/0x1b > > [] set_dentry_child_flags+0x5a/0x119 > > [] remove_watch_no_event+0x56/0x64 > > [] inotify_remove_watch_locked+0x12/0x34 > > [] inotify_rm_wd+0x75/0x93 > > [] sys_inotify_rm_watch+0x40/0x58 > > [] 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