From: Greg KH <gregkh@linuxfoundation.org>
To: "Hans Müller" <schreibemirhalt@gmail.com>
Cc: arve@android.com, christian@brauner.io, hch@lst.de,
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 08:29:51 +0200 [thread overview]
Message-ID: <YqrN38V/qS9ljk8+@kroah.com> (raw)
In-Reply-To: <3f8d25aa-17a6-e6aa-4b6d-d3388ef35201@gmail.com>
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
next prev parent reply other threads:[~2022-06-16 6:29 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 [this message]
2022-06-16 6:31 ` Christoph Hellwig
2022-06-16 8:34 ` Greg KH
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=YqrN38V/qS9ljk8+@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