linux-kernel - Re: Forked android kernel development from linux kernel mainline

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 6 Nov 2010 16:52:26 -0700 (PDT)
From:	david@...g.hm
To:	"Ted Ts'o" <tytso@....edu>
cc:	Anca Emanuel <anca.emanuel@...il.com>, Greg KH <greg@...ah.com>,
	Elvis Dowson <elvis.dowson@....com>,
	Janakiram Sistla <janakiram.sistla@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline

On Sat, 6 Nov 2010, Ted Ts'o wrote:

> On Sat, Nov 06, 2010 at 09:40:34PM +0200, Anca Emanuel wrote:
>> I think you need to see this: https://review.source.android.com/#change,18761
>> And this: http://galaxytab.samsungmobile.com/
>
> What about them?  Yes, the Android developers are pushing changes to
> mainstream where it makes sense; they were doing this before the
> wakelocks contrversy, and they're continuing to do it now.  But in the
> case of wakelocks, it may be that it's going to have to be a case of
> "agree to disagree".
>
> All distributions, including Red Hat and SLES has in the shipped
> product with patches that have never hit mainstream, and in some
> cases, will never get merged with mainstream.  A good example in the
> past was the 4G/4G patch.  Another one, which is still on-going, is
> the Systemtap/utrace patches.  Yet no one is killing megawatts worth
> of electrons about how Red Hat and SLES are forking the kernel.  They
> push patches upstream where they can, and where they can't --- they do
> what they need to do to satisify and delight their customers.
>
> (Heck, Sony is still using a 2.2 kernel for some of their products
> with a huge bunch of patches and no one is toasting them for forking
> the kernel....)

the difference is that these other patches that you are talking about do 
not result in incompatible userspace (or at least, they don't except for 
very specialied apps).

also, none of these other patches resulted in device drivers developed for 
a distro being incompatible with mainline.

I think that the concerns from technical folks (as opposed to 
journalists/bloggers) would go down drastically if there was some 
acceptable way for the incompatible bits (like wakelocks) could be 
stubbed out so that the rest of the things could be moved easily.

David Lang

> Move along, there's nothing to see.  Other that money for
> journalists/bloggers who are gunning for advertising clicks by
> whipping up controversy where IMHO, none deserves to exist.
>
> 					- Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/