From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jann Horn <jannh@google.com>,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
"Paul E. McKenney" <paulmck@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
Adam Zabrocki <pi3@pi3.com.pl>,
kernel list <linux-kernel@vger.kernel.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Oleg Nesterov <oleg@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Bernd Edlinger <bernd.edlinger@hotmail.de>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable <stable@vger.kernel.org>, Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [PATCH] signal: Extend exec_id to 64bits
Date: Thu, 02 Apr 2020 08:11:31 -0500 [thread overview]
Message-ID: <877dyym3r0.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <CAHk-=whks0iE1f=Ka0_vo2PYg774P7FA8Y30YrOdUBGRH-ch9A@mail.gmail.com> (Linus Torvalds's message of "Wed, 1 Apr 2020 19:05:59 -0700")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> tasklist_lock is aboue the hottest lock there is in all of the kernel.
Do you know code paths you see tasklist_lock being hot?
I am looking at some of the exec/signal/ptrace code paths because they
get subtle corner case wrong like a threaded exec deadlocking when
straced.
If the performance problems are in the same neighbourhood I might be
able to fix those problems while I am in the code.
Eric
next prev parent reply other threads:[~2020-04-02 13:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 21:50 Curiosity around 'exec_id' and some problems associated with it Adam Zabrocki
2020-03-29 22:43 ` Kees Cook
2020-03-30 8:34 ` Oleg Nesterov
2020-03-31 4:29 ` Adam Zabrocki
2020-04-01 20:47 ` [PATCH] signal: Extend exec_id to 64bits Eric W. Biederman
2020-04-01 20:55 ` Linus Torvalds
2020-04-01 21:03 ` Eric W. Biederman
2020-04-01 23:37 ` Jann Horn
2020-04-01 23:51 ` Linus Torvalds
2020-04-01 23:55 ` Linus Torvalds
2020-04-02 1:35 ` Jann Horn
2020-04-02 2:05 ` Linus Torvalds
2020-04-02 13:11 ` Eric W. Biederman [this message]
2020-04-02 18:06 ` Linus Torvalds
2020-04-02 4:46 ` Jann Horn
2020-04-02 14:14 ` Eric W. Biederman
2020-04-03 2:11 ` Adam Zabrocki
2020-04-02 7:19 ` Kees Cook
2020-04-02 7:22 ` Bernd Edlinger
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=877dyym3r0.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bernd.edlinger@hotmail.de \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=j.alglave@ucl.ac.uk \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=luto@amacapital.net \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pi3@pi3.com.pl \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.