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

Hi,

On 10/08/06, Mingming Cao <[email protected]> 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

>
> Thanks,
> Mingming

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-fsdevel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html