linux-kernel - Re: [PATCH AUTOSEL 4.20 36/81] binder: fix CONFIG_ANDROID_BINDER

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:   Thu, 28 Feb 2019 16:24:07 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Sasha Levin <sashal@...nel.org>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        devel@...verdev.osuosl.org, Martijn Coenen <maco@...gle.com>,
        Christian Brauner <christian.brauner@...ntu.com>,
        Christian Brauner <christian@...uner.io>
Subject: Re: [PATCH AUTOSEL 4.20 36/81] binder: fix
 CONFIG_ANDROID_BINDER_DEVICES

On Thu, Feb 28, 2019 at 10:07:28AM -0500, Sasha Levin wrote:
> From: Christian Brauner <christian@...uner.io>
> 
> [ Upstream commit 793c8232937610ae00bc174b87d7fc324346eaea ]
> 
> Several users have tried to only rely on binderfs to provide binder devices
> and set CONFIG_ANDROID_BINDER_DEVICES="" empty. This is a great use-case of
> binderfs and one that was always intended to work. However, this is
> currently not possible since setting CONFIG_ANDROID_BINDER_DEVICES="" emtpy
> will simply panic the kernel:

There is no binderfs on 4.20, so this patch is not needed on anything
older than 5.0.

Please drop it from your queues.

thanks,

greg k-h