From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Daniel J Blueman <daniel@quora.org>, linux-ext4@vger.kernel.org
Subject: Re: 3.9-rc6 ext4: free_rb_tree_fname oops
Date: Mon, 24 Jun 2013 21:28:04 +0800 [thread overview]
Message-ID: <20130624132804.GA7709@gmail.com> (raw)
In-Reply-To: <20130624123726.GA17012@thunk.org>
On Mon, Jun 24, 2013 at 08:37:26AM -0400, Theodore Ts'o wrote:
> (LKML and Linux-fsdevel moved to bcc)
>
> On Mon, Jun 24, 2013 at 02:34:00PM +0800, Daniel J Blueman wrote:
> > On 16 April 2013 15:37, Daniel J Blueman <daniel@quora.org> wrote:
> > > When using e4defrag on a ext4 filesystem created a month ago, I ran
> > > into this fatal page fault [1]
> > > while running e4defrag on 3.9-rc6 (Ubuntu mainline).
> > >
> > > e2fsdump output is at http://quora.org/2012/e2fsdump.txt ; let me know
> > > if you need any more info.
> >
> > With 3.9.6 mainline, I got the exact same protection fault at
> > free_rb_tree_fname() from ext4_htree_free_dir_info() [1]. This
> > suggests use-after-free, as there's no pagetable mapping.
> >
> > There is nothing special with my setups, so there is fair chance it's
> > reproducible there with e4defrag on a few month old filesystem and
> > recent kernels.
>
> Sounds like we may have a bug in how the new extent_status tree code
> was integrated into fs/ext4/move_extent.c. Zheng, if you could take a
> look I'd really appreciate it.
Sorry for the late reply. I will take a close look at this bug.
Regards,
- Zheng
next prev parent reply other threads:[~2013-06-24 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 7:37 3.9-rc6 ext4: free_rb_tree_fname oops Daniel J Blueman
2013-04-22 11:57 ` Zheng Liu
2013-06-24 6:34 ` Daniel J Blueman
2013-06-24 12:37 ` Theodore Ts'o
2013-06-24 13:28 ` Zheng Liu [this message]
2013-06-24 12:37 ` Theodore Ts'o
2013-07-10 2:06 ` Zheng Liu
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=20130624132804.GA7709@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=daniel@quora.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.