[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiOdXfMa35bwCNfCNSsAndO-hFmsSNRWEEDziA1iDYGjg@mail.gmail.com>
Date: Thu, 30 Apr 2020 06:47:41 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Bernd Edlinger <bernd.edlinger@...mail.de>
Cc: Jann Horn <jannh@...gle.com>, Oleg Nesterov <oleg@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Waiman Long <longman@...hat.com>,
Ingo Molnar <mingo@...nel.org>, Will Deacon <will@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alexey Gladkov <gladkov.alexey@...il.com>
Subject: Re: [GIT PULL] Please pull proc and exec work for 5.7-rc1
On Thu, Apr 30, 2020 at 6:39 AM Bernd Edlinger
<bernd.edlinger@...mail.de> wrote:
>
> Excuse me, but what in my /proc folder there is no attr/something
> is there a procfs equivalent of pthread_attach ?
>
> What exactly is "attr/something" ?
Anything that uses that proc_pid_attr_write().
Which you should have realized, since you wrote the patch that changed
that function to return -EAGAIN.
That's
/proc/<pid>/attr/{current,exec,fscreate,keycreate,prev,sockcreate}
and some smack files.
Your patch definitely made them return -EINVAL if they happen in that
execve() black hole, instead of waiting for the execve() to just
complete and then just work.
Dropping a lock really is broken. It';s broken even if you then set a
flag saying "I dropped the lock, now you can't use it".
Linus
Powered by blists - more mailing lists