From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/2] Signal-related changes for 3.19
Date: Tue, 28 Oct 2014 15:13:30 -0700 [thread overview]
Message-ID: <20141028221330.GA27479@linux.vnet.ibm.com> (raw)
Hello!
This series updates RCU handling in signals:
1. Prevents a possible very long RCU read-side critical section
in kill_pid_info().
2. Explain why the "obviously buggy" freeing of sighand by
__cleanup_sighand() without an RCU grace period really isn't
buggy, courtesy of Oleg Nesterov.
Thanx, Paul
------------------------------------------------------------------------
b/kernel/fork.c | 5 ++++-
b/kernel/signal.c | 42 +++++++++++++++++++++++++-----------------
2 files changed, 29 insertions(+), 18 deletions(-)
next reply other threads:[~2014-10-28 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 22:13 Paul E. McKenney [this message]
2014-10-28 22:13 ` [PATCH tip/core/rcu 1/2] signal: Exit RCU read-side critical section on each pass through loop Paul E. McKenney
2014-10-28 22:13 ` [PATCH tip/core/rcu 2/2] signal: Document the RCU protection of ->sighand Paul E. McKenney
2014-10-29 2:13 ` [PATCH tip/core/rcu 0/2] Signal-related changes for 3.19 Pranith Kumar
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=20141028221330.GA27479@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox