From: tip-bot for Oleg Nesterov <oleg@redhat.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
torvalds@linux-foundation.org, a.p.zijlstra@chello.nl,
davej@redhat.com, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org, tglx@linutronix.de, oleg@redhat.com
Subject: [tip:core/urgent] task_work: Revert " hold task_lock around checks in keyctl"
Date: Thu, 13 Sep 2012 23:10:26 -0700 [thread overview]
Message-ID: <tip-b3f68f16dbcde6fcdf0fd27695391ff7e9d41233@git.kernel.org> (raw)
In-Reply-To: <20120826191214.GA4231@redhat.com>
Commit-ID: b3f68f16dbcde6fcdf0fd27695391ff7e9d41233
Gitweb: http://git.kernel.org/tip/b3f68f16dbcde6fcdf0fd27695391ff7e9d41233
Author: Oleg Nesterov <oleg@redhat.com>
AuthorDate: Sun, 26 Aug 2012 21:12:14 +0200
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Thu, 13 Sep 2012 16:47:36 +0200
task_work: Revert "hold task_lock around checks in keyctl"
This reverts commit d35abdb28824cf74f0a106a0f9c6f3ff700a35bf.
task_lock() was added to ensure exit_mm() and thus exit_task_work() is
not possible before task_work_add().
This is wrong, task_lock() must not be nested with write_lock(tasklist).
And this is no longer needed, task_work_add() now fails if it is called
after exit_task_work().
Reported-by: Dave Jones <davej@redhat.com>
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: http://lkml.kernel.org/r/20120826191214.GA4231@redhat.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
security/keys/keyctl.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/security/keys/keyctl.c b/security/keys/keyctl.c
index 3364fbf..6cfc647 100644
--- a/security/keys/keyctl.c
+++ b/security/keys/keyctl.c
@@ -1486,7 +1486,6 @@ long keyctl_session_to_parent(void)
oldwork = NULL;
parent = me->real_parent;
- task_lock(parent);
/* the parent mustn't be init and mustn't be a kernel thread */
if (parent->pid <= 1 || !parent->mm)
goto unlock;
@@ -1530,7 +1529,6 @@ long keyctl_session_to_parent(void)
if (!ret)
newwork = NULL;
unlock:
- task_unlock(parent);
write_unlock_irq(&tasklist_lock);
rcu_read_unlock();
if (oldwork)
next prev parent reply other threads:[~2012-09-14 6:10 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 20:36 lockdep trace from posix timers Dave Jones
2012-07-27 16:20 ` Dave Jones
2012-08-16 12:54 ` Ming Lei
2012-08-16 14:03 ` Dave Jones
2012-08-16 18:07 ` Peter Zijlstra
2012-08-17 15:14 ` Oleg Nesterov
2012-08-17 15:17 ` Oleg Nesterov
2012-08-17 16:40 ` task_work_add() should not succeed unconditionally (Was: lockdep trace from posix timers) Oleg Nesterov
2012-08-20 7:15 ` lockdep trace from posix timers Peter Zijlstra
2012-08-20 11:44 ` Peter Zijlstra
2012-08-20 11:46 ` Peter Zijlstra
2012-08-20 11:50 ` Peter Zijlstra
2012-08-20 12:19 ` Steven Rostedt
2012-08-20 12:20 ` Peter Zijlstra
2012-08-20 14:59 ` Oleg Nesterov
2012-08-20 15:10 ` Peter Zijlstra
2012-08-20 15:27 ` Peter Zijlstra
2012-08-20 15:32 ` Oleg Nesterov
2012-08-20 15:46 ` Peter Zijlstra
2012-08-20 15:58 ` Oleg Nesterov
2012-08-20 16:03 ` Peter Zijlstra
2012-08-20 15:05 ` Oleg Nesterov
2012-08-20 15:12 ` Peter Zijlstra
2012-08-20 15:41 ` Oleg Nesterov
2012-08-20 15:56 ` Peter Zijlstra
2012-08-20 16:10 ` Oleg Nesterov
2012-08-20 16:19 ` Peter Zijlstra
2012-08-20 16:23 ` Oleg Nesterov
2012-08-21 18:27 ` Oleg Nesterov
2012-08-21 18:34 ` Oleg Nesterov
2012-08-24 18:56 ` Oleg Nesterov
2012-08-26 19:11 ` [PATCH 0/4] (Was: lockdep trace from posix timers) Oleg Nesterov
2012-08-26 19:12 ` [PATCH 1/4] task_work: make task_work_add() lockless Oleg Nesterov
2012-09-14 6:08 ` [tip:core/urgent] task_work: Make " tip-bot for Oleg Nesterov
2012-09-24 19:27 ` [PATCH 1/4] task_work: make " Geert Uytterhoeven
2012-09-24 20:37 ` Oleg Nesterov
2012-08-26 19:12 ` [PATCH 2/4] task_work: task_work_add() should not succeed after exit_task_work() Oleg Nesterov
2012-09-14 6:09 ` [tip:core/urgent] " tip-bot for Oleg Nesterov
2012-08-26 19:12 ` [PATCH 3/4] task_work: revert d35abdb2 "hold task_lock around checks in keyctl" Oleg Nesterov
2012-09-14 6:10 ` tip-bot for Oleg Nesterov [this message]
2012-08-26 19:12 ` [PATCH 4/4] task_work: simplify the usage in ptrace_notify() and get_signal_to_deliver() Oleg Nesterov
2012-09-14 6:11 ` [tip:core/urgent] task_work: Simplify " tip-bot for Oleg Nesterov
2012-09-06 18:01 ` [PATCH 0/4] (Was: lockdep trace from posix timers) Oleg Nesterov
2012-09-06 18:35 ` Peter Zijlstra
2012-09-07 13:13 ` Oleg Nesterov
2012-08-28 16:29 ` lockdep trace from posix timers Peter Zijlstra
2012-08-28 17:01 ` Oleg Nesterov
2012-08-28 17:12 ` Oleg Nesterov
2012-08-28 17:28 ` Peter Zijlstra
2012-08-29 15:25 ` Oleg Nesterov
2012-08-20 14:55 ` Oleg Nesterov
2012-08-20 15:43 ` Oleg Nesterov
2012-08-20 15:48 ` Peter Zijlstra
2012-08-20 15:58 ` Oleg Nesterov
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=tip-b3f68f16dbcde6fcdf0fd27695391ff7e9d41233@git.kernel.org \
--to=oleg@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).