Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 12 Feb 2020 13:02:40 -0800
From: Linus Torvalds <>
To: Al Viro <>
Cc: "Eric W. Biederman" <>, LKML <>, 
	Kernel Hardening <>, Linux API <>, 
	Linux FS Devel <>, 
	Linux Security Module <>, 
	Akinobu Mita <>, Alexey Dobriyan <>, 
	Andrew Morton <>, Andy Lutomirski <>, 
	Daniel Micay <>, Djalal Harouni <>, 
	"Dmitry V . Levin" <>, Greg Kroah-Hartman <>, 
	Ingo Molnar <>, "J . Bruce Fields" <>, 
	Jeff Layton <>, Jonathan Corbet <>, 
	Kees Cook <>, Oleg Nesterov <>, 
	Solar Designer <>
Subject: Re: [PATCH v8 07/11] proc: flush task dcache entries from all procfs instances

On Wed, Feb 12, 2020 at 12:41 PM Al Viro <> wrote:
> On Wed, Feb 12, 2020 at 08:38:33PM +0000, Al Viro wrote:
> >
> > Wait, I thought the whole point of that had been to allow multiple
> > procfs instances for the same userns?  Confused...
> s/userns/pidns/, sorry

Right, but we still hold the ref to it here...

[ Looks more ]

Oooh. No we don't. Exactly because we don't hold the lock, only the
rcu lifetime, the ref can go away from under us. I see what your
concern is.

Ouch, this is more painful than I expected - the code flow looked so
simple. I really wanted to avoid a new lock during process shutdown,
because that has always been somewhat painful.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.