From: Willy Tarreau <w@1wt.eu>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: zhuyj <zyjzyj2000@gmail.com>,
linux-ext4@vger.kernel.org, stable@kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: Ext4:can not rm directories on 2.6.3x
Date: Fri, 15 Mar 2013 15:56:04 +0100 [thread overview]
Message-ID: <20130315145604.GA5048@1wt.eu> (raw)
In-Reply-To: <20130315145314.GB7403@thunk.org>
On Fri, Mar 15, 2013 at 10:53:14AM -0400, Theodore Ts'o wrote:
> On Fri, Mar 15, 2013 at 03:16:52PM +0800, zhuyj wrote:
> > Hi, all
> >
> > The two patches can fix this problem.
> > ext4: Fix fs corruption when make_indexed_dir() fails
> > ext4: don't dereference null pointer when make_indexed_dir() fails
>
> Thanks, Zhujh for figuring this out. Those two patches weren't
> taggled with cc: stable@vger.kernel.org, but they probably should have
> been. Since they first appeared in v3.0, the two long-term stable
> kernels that would benefit with these patches are v3.0.x and v3.2.x.
>
> Willy, Paul, would you consider cherry-picking the following commits
> for your respective stable kernels?
>
> git cherry-pick 7ad8e4e6ae2a7c95445ee1715b1714106fb95037
> git cherry-pick 6976a6f2acde2b0443cd64f1d08af90630e4ce81
Yes of course !
Thank you Ted!
Willy
next prev parent reply other threads:[~2013-03-15 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 6:58 Inactive memory keep growing and how to release it? Lenky Gao
2013-03-12 7:41 ` a problem about ext4 zhuyj
2013-03-12 7:49 ` zhuyj
2013-03-12 8:13 ` zhuyj
2013-03-12 13:42 ` Theodore Ts'o
2013-03-13 3:24 ` Ext4:can not rm directories on 2.6.3x zhuyj
2013-03-15 7:16 ` zhuyj
2013-03-15 14:53 ` Theodore Ts'o
2013-03-15 14:56 ` Willy Tarreau [this message]
2013-03-15 14:59 ` Theodore Ts'o
2013-03-15 15:12 ` Paul Gortmaker
2013-03-12 8:37 ` Inactive memory keep growing and how to release it? Zheng Liu
2013-03-12 8:48 ` Lenky Gao
2013-03-14 8:00 ` Lenky Gao
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=20130315145604.GA5048@1wt.eu \
--to=w@1wt.eu \
--cc=linux-ext4@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=stable@kernel.org \
--cc=tytso@mit.edu \
--cc=zyjzyj2000@gmail.com \
/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).