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
