linux-kernel - Re: [PATCH 0/5] Forking ext4 filesystem and JBD2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1156012970.9346.1.camel@localhost.localdomain>
Date:	Sat, 19 Aug 2006 14:42:50 -0400
From:	John McCutchan <john@...nmccutchan.com>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	cmm@...ibm.com, akpm@...l.org, linux-kernel@...r.kernel.org,
	ext2-devel@...ts.sourceforge.net, linux-fsdevel@...r.kernel.org,
	John McCutchan <ttb@...tacle.dhs.org>,
	Robert Love <rml@...ell.com>
Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2

On Thu, 2006-10-08 at 17:15 +0200, Michal Piotrowski wrote:
> On 10/08/06, Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote:
> > Hi,
> >
> > On 10/08/06, Mingming Cao <cmm@...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 just ran your loop of mounting/unmounting a fs for over an hour and I
can't reproduce this.

-- 
John McCutchan <john@...nmccutchan.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/