lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sun, 3 Feb 2013 07:55:30 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Wuqixuan <wuqixuan@...wei.com>
Cc:	Andreas Dilger <adilger@...ger.ca>, "tm@....ma" <tm@....ma>,
	"xiaoqiangnk@...il.com" <xiaoqiangnk@...il.com>,
	Lizefan <lizefan@...wei.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: 答复: Help to know the stable ver
 of ext4 for commercial app.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists