linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Wuqixuan <wuqixuan@huawei.com>
Cc: Andreas Dilger <adilger@dilger.ca>, "tm@tao.ma" <tm@tao.ma>,
	"xiaoqiangnk@gmail.com" <xiaoqiangnk@gmail.com>,
	Lizefan <lizefan@huawei.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: 答复: Help to know the stable ver of ext4 for commercial app.
Date: Sun, 3 Feb 2013 07:55:30 -0500	[thread overview]
Message-ID: <20130203125530.GA4584@thunk.org> (raw)
In-Reply-To: <BB7C62C2B0732E4DA93834A501E8464544E62883@SZXEML519-MBS.china.huawei.com>

On Sun, Feb 03, 2013 at 07:13:19AM +0000, Wuqixuan wrote:
> 
>      Thanks, I will check and compare the latest RHEL6 2.6.32 ext4 and the 2.6.32.x and 2.6.34.x in the vanilla kernel. 

I think you will find that they are quite different.

>      BTW, even now I can see in 2.6.32.x version in vanilla kernel,
>still there are some patches are checked in. But not very
>frequently. There are 5 in 2011, and 4 in 2012.

In general, these are the patches which applied trivially, so it woud
not require any special expertise to backport them.  In many cases,
these are what could be called "one-liners".

>So do you mean Redhat
>does not checkin all the patches which backport in RHEL6 to the
>vanilla kernel ?

That's correct.  It is not their responsibility to update generic
2.6.32.x kernels.  Keep in mind that when distributions talk about
"upstream first", what they mean is that new features and new drivers
get developed in the tip of the latest development upstream kernel,
and then get backported to whatever ancient "enterprise kernel" (i.e.,
2.6.32.x, et. al) that their customers pay $$$ to for them to support.

In some cases, when distributions fix a bug in their ancient 2.6.32.x
kernels for one of their paying customers, they will make point of
checking to see if the bug still applies in the development upstream
kernel, and if it does, they will submit a patch to the upstream
kernel.  Those are the distributions I will tend to help out.  But
when a company like Montavista comes out of nowhere, without having
contributed anything to ext4, and then asks for free engineering help
for their commercial kernel, it's likely that they free engineering
help they will receive will be minimal....

>      And do you know how about the stability of other distrubutions, like Windriver 4 sp3 ? 

You should really ask Windriver, and not the upstream lists.  Keep in
mind that for an upstream development engineer, commercial kernels
tend to be considered evolutionary dead ends....

							- Ted

  parent reply	other threads:[~2013-02-03 12:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-02  2:30 Help to know the stable ver of ext4 for commercial app Wuqixuan
2013-02-02  3:23 ` Theodore Ts'o
2013-02-02  7:20   ` Wuqixuan
2013-02-02 18:08     ` Andreas Dilger
     [not found]       ` <BB7C62C2B0732E4DA93834A501E8464544E62883@SZXEML519-MBS.china.huawei.com>
2013-02-03 12:55         ` Theodore Ts'o [this message]
     [not found]       ` <BB7C62C2B0732E4DA93834A501E8464544E628B1@SZXEML519-MBS.china.huawei.com>
2013-02-04 17:52         ` qixuan wu
2013-02-05  1:17           ` Li Zefan
2013-02-05 15:20           ` Eric Sandeen
2013-02-02 22:43     ` Theodore Ts'o
     [not found]       ` <BB7C62C2B0732E4DA93834A501E8464544E628A6@SZXEML519-MBS.china.huawei.com>
2013-02-03 17:39         ` qixuan wu
2013-02-03 22:52           ` Theodore Ts'o
2013-02-04 17:53             ` qixuan wu

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=20130203125530.GA4584@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=tm@tao.ma \
    --cc=wuqixuan@huawei.com \
    --cc=xiaoqiangnk@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).