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

Date:   Thu, 16 Jun 2022 10:34:11 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Christoph Hellwig <hch@....de>
Cc:     Hans Müller <schreibemirhalt@...il.com>,
        arve@...roid.com, christian@...uner.io, 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 08:31:04AM +0200, Christoph Hellwig wrote:
> On Thu, Jun 16, 2022 at 08:29:51AM +0200, Greg KH wrote:
> > 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...)
> 
> I'm very much against this.  ashmem is a mess and we should not maintain
> it for some kind of retro computing group.

I totally agree, and was hinting that if someone actually had the skill
to maintain ashmem, they would know it is easier to just fix the
userspace code instead :)