From: Theodore Ts'o <tytso@mit.edu>
To: zhuyj <zyjzyj2000@gmail.com>
Cc: zhuyj <zyjzyj2000@gmail.xom>, linux-ext4@vger.kernel.org
Subject: Re: a problem about ext4.
Date: Tue, 12 Mar 2013 09:42:29 -0400 [thread overview]
Message-ID: <20130312134229.GJ18595@thunk.org> (raw)
In-Reply-To: <513EDC2B.9020604@gmail.xom>
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-12 13:42 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 [this message]
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
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=20130312134229.GJ18595@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=zyjzyj2000@gmail.com \
--cc=zyjzyj2000@gmail.xom \
/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).