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  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:	Mon, 20 Oct 2014 06:04:50 +0800
From:	Greg Kroah-Hartman <>
To:	Christoph Hellwig <>
Cc:, Anup Patel <>,,,
	Arve Hj?nnev?g <>,
	Santosh Shilimkar <>,
	Rebecca Schultz Zavin <>,
	John Stultz <>,
	Sumit Semwal <>,
	Christoffer Dall <>
Subject: Re: [PATCH] staging: android: binder: move to the "real" part of the

On Fri, Oct 17, 2014 at 02:43:29AM -0700, Christoph Hellwig wrote:
> On Thu, Oct 16, 2014 at 02:47:41PM +0200, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman <>
> > 
> > The Android binder code has been "stable" for many years now.  No matter
> > what comes in the future, we are going to have to support this API, so
> > might as well move it to the "real" part of the kernel as there's no
> > real work that needs to be done to the existing code.
> NAK.  It's complete rubbish and does things to the FD code that it
> really shouldn't.  Android needs to completely redo the interface, and
> there's been absolutely no work towards that.

There is now work to resolve the interface, it requires someone who has
the rights to push to Android userspace.  But that is going to be a
"total rewrite", and until then, this code needs to be used, no matter
how much we hate this.

> This is exactly the sort of attitude I feared about when you started the
> whole staging concepts, and it sounds like a good reason to disband
> staging entirely, given that it's been mostly useless except for
> boasting peoples commit statistics.

I know you hate staging, which is fine, it's not there for you.  It's
there for others, and so much good stuff has happened with it, that I'm
not going to give it up.

But this code is different.  It's something like a random driver that a
distro has been carrying for 5+ years that it has to ship due to
userspace that relies on it, so the api can't be changed.  We accept
drivers like that at times, and we don't drop really old and crappy
drivers either, as long as someone is using it, and it is

I'll step up to maintain this and handle the interactions between grumpy
kernel developers who look at the code, and the Android developers who
are stuck with this monstrosity.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists