[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5FBCBE569E134E4CA167B91C0A77FD610198F91F70@EXMBX-SZMAIL022.tencent.com>
Date: Tue, 13 Nov 2018 08:12:08 +0000
From: chouryzhou(周威) <chouryzhou@...cent.com>
To: Christian Brauner <christian@...uner.io>,
Todd Kjos <tkjos@...gle.com>, Martijn Coenen <maco@...roid.com>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arve Hjønnevåg <arve@...roid.com>,
Todd Kjos <tkjos@...roid.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"dave@...olabs.net" <dave@...olabs.net>,
"open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V4] binder: ipc namespace support for android binder
> I have not received an answer to my questions in the last version of this patch
> set. Also it would be good if I could be Cc'ed by default. I can't hunt down all
> patches.
> I do not know of any kernel entity, specifically devices, that change namespaces
> on open().
> This seems like an invitation for all kinds of security bugs.
> A device node belongs to one namespace only which is attached to the
> underlying kobject. Opening the device should never change that.
> Please look at how mqueue or shm are doing this. They don't change
> namespaces on open either.
> I have to say that is one of the main reasons why I disagree with that design.
>
>
If we must return the same context when every open in proc, we can only isolate
binder with mnt namespace instead of ipc namespace, what do you think, Todd?
Powered by blists - more mailing lists