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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 11 Mar 2019 13:23:18 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.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 04:24:07PM +0100, Greg Kroah-Hartman wrote:
>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.

Heh, I knew binder was there for a while, didn't know binderfs is
something new. Now dropped, thanks!

--
Thanks,
Sasha