From: zhuyj <zyjzyj2000@gmail.com>
To: zhuyj <zyjzyj2000@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Ext4:can not rm directories on 2.6.3x
Date: Fri, 15 Mar 2013 15:16:52 +0800 [thread overview]
Message-ID: <5142CAE4.3070400@gmail.xom> (raw)
In-Reply-To: <513FF163.7080606@gmail.xom>
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
If any one comes across this problem, he can apply the above two patches.
Zhuyj
On 03/13/2013 11:24 AM, zhuyj wrote:
> OK. Thanks a lot.
> This bug can happen on Ubuntu 11.04,10.10 with kernel 2.6.3x.
> Follow the above steps, this bug can be reproduced.
>
> Anyone has the same experience?
>
> On 03/12/2013 09:42 PM, Theodore Ts'o wrote:
>> On Tue, Mar 12, 2013 at 03:41:31PM +0800, zhuyj wrote:
>>> If I use kernel>=3.0, this will not occur.
>> Sounds like this is a problem in 2.6.39 that has since been fixed in
>> newer kernels.
>>
>>> So is this is a bug?
>> Sure looks like it's a bug. :-)
>>
>> There are so many distributions and other old embedded systems, etc.,
>> using older kernels that there's just no way that upstream developers
>> can try to debug every single older kernel --- and 2.6.39 isn't even a
>> kernel that is being supported by a volunteer as a long-term supported
>> kernel.
>>
>> See http://www.kernel.org for a list of kernels which are supported as
>> long-term kernels, and even then, please remember that unless fixes
>> are automatically backported, or someone manually backports a fix that
>> doesn't automatically apply to an older kernel, it's not going to
>> happen.....
>>
>> Regards,
>>
>> - Ted
>>
>> P.S. Your problem appears to be completely unrelated to the thread
>> which you replied to. This makes it hard for us to keep track of
>> questions/bug reports which users submit.
>>
>
>
next prev parent reply other threads:[~2013-03-15 7:24 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 [this message]
2013-03-15 14:53 ` Theodore Ts'o
2013-03-15 14:56 ` Willy Tarreau
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=5142CAE4.3070400@gmail.xom \
--to=zyjzyj2000@gmail.com \
--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 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).