From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: cmm@us.ibm.com
Cc: 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>
Subject: Re: [PATCH 0/5] Forking ext4 filesystem and JBD2
Date: Thu, 10 Aug 2006 16:02:47 +0200 [thread overview]
Message-ID: <6bffcb0e0608100702m1ad3925bw3e5f0e4804210fc9@mail.gmail.com> (raw)
In-Reply-To: <1155172597.3161.72.camel@localhost.localdomain>
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
>
> Thanks,
> Mingming
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
next prev parent reply other threads:[~2006-08-10 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 1:16 [PATCH 0/5] Forking ext4 filesystem and JBD2 Mingming Cao
2006-08-10 5:58 ` Jeff Garzik
2006-08-10 16:33 ` Mingming Cao
2006-08-10 17:00 ` Andrew Morton
2006-08-14 21:44 ` Pavel Machek
2006-08-15 19:06 ` Jeff Garzik
2006-08-10 14:02 ` Michal Piotrowski [this message]
2006-08-10 15:15 ` Michal Piotrowski
[not found] ` <1155236801.3162.1.camel@localhost.localdomain>
2006-08-10 19:06 ` John McCutchan
2006-08-10 19:06 ` John McCutchan
2006-08-10 19:06 ` John McCutchan
[not found] ` <1156012970.9346.1.camel@localhost.localdomain>
2006-08-19 18:42 ` John McCutchan
2006-08-19 21:17 ` Michal Piotrowski
2006-08-19 18:42 ` John McCutchan
2006-08-19 18:42 ` John McCutchan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bffcb0e0608100702m1ad3925bw3e5f0e4804210fc9@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=ttb@tentacle.dhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).