linux-kernel - Re: [PATCH] staging: remove ashmem

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]

Message-ID: <YqrN38V/qS9ljk8+@kroah.com>
Date:   Thu, 16 Jun 2022 08:29:51 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Hans Müller <schreibemirhalt@...il.com>
Cc:     arve@...roid.com, christian@...uner.io, hch@....de,
        hridya@...gle.com, joel@...lfernandes.org,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org, maco@...roid.com,
        surenb@...gle.com, tkjos@...roid.com
Subject: Re: [PATCH] staging: remove ashmem

On Thu, Jun 16, 2022 at 07:27:48AM +0200, Hans Müller wrote:
> It is not only Android itself that broke but also Anbox
> (https://en.wikipedia.org/wiki/Anbox):
> https://github.com/anbox/anbox/issues/2042
> 
> I use that regularly on my system... I know there is Waydroid and I do use
> it sometimes but it is not a full replacement (especially since it makes the
> whole system slower over time and spams the tty).
> 
> Could you consider reverting that change until the Anbox people found a way
> which allows Anbox to not depend on ashmem anymore?

That is a "Android 7-based" system?  That's old, how are they supporting
that anymore with the security stuff that has happened since then?

Anyway, if this were to come back, I need a maintainer who agrees to
maintain it and fix and support it.  Are you able to do that?  If so, I
think it would probably be easier to fix up anbox to use memfd instead,
is anyone doing that (I couldn't figure that out from the github
issue...)

thanks,

greg k-h