From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Hans Müller" <schreibemirhalt@gmail.com>,
arve@android.com, christian@brauner.io, hridya@google.com,
joel@joelfernandes.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, maco@android.com, surenb@google.com,
tkjos@android.com
Subject: Re: [PATCH] staging: remove ashmem
Date: Thu, 16 Jun 2022 10:34:11 +0200 [thread overview]
Message-ID: <YqrrA0ddWsRi2vH7@kroah.com> (raw)
In-Reply-To: <20220616063104.GA5494@lst.de>
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 :)
prev parent reply other threads:[~2022-06-16 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 12:34 Christoph Hellwig
2022-03-15 13:22 ` Greg Kroah-Hartman
2022-06-16 5:27 ` Hans Müller
2022-06-16 6:29 ` Greg KH
2022-06-16 6:31 ` Christoph Hellwig
2022-06-16 8:34 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YqrrA0ddWsRi2vH7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=hch@lst.de \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maco@android.com \
--cc=schreibemirhalt@gmail.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox