From: Arthur Jones <ajones@riverbed.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: ext3: kernel BUG at fs/jbd/journal.c:412!
Date: Thu, 6 Nov 2008 08:12:27 -0800 [thread overview]
Message-ID: <20081106161227.GA9254@ajones-laptop.nbttech.com> (raw)
In-Reply-To: <20081106155025.GE25194@skywalker>
Hi Aneesh, ...
On Thu, Nov 06, 2008 at 07:50:25AM -0800, Aneesh Kumar K.V wrote:
> I get this with ext4-patchqueue. I guess we have some ext3 patches queued there.
This could be related to a patch I just posted.
I'd like to try to reproduce this. What is the
ext4-patchqueue? What were you running that caused
this to pop up?
See the thread on linux-ext4 called "ext3: slow symlink corruption
on umount" for details on how this patch came about...
Thanks...
Arthur
next prev parent reply other threads:[~2008-11-06 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 15:50 ext3: kernel BUG at fs/jbd/journal.c:412! Aneesh Kumar K.V
2008-11-06 16:12 ` Arthur Jones [this message]
2008-11-06 16:43 ` Aneesh Kumar K.V
2008-11-06 17:13 ` Theodore Tso
2008-11-06 17:16 ` Aneesh Kumar K.V
2008-11-06 17:32 ` Theodore Tso
2008-11-06 17:38 ` Aneesh Kumar K.V
2008-11-06 17:23 ` Arthur Jones
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=20081106161227.GA9254@ajones-laptop.nbttech.com \
--to=ajones@riverbed.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.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