From: Oleg Nesterov <oleg@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
". James Morris" <jmorris@namei.org>,
linux-security-module@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: [PATCH 2/4] task_work: don't rely on PF_EXITING
Date: Wed, 27 Jun 2012 20:37:57 +0200 [thread overview]
Message-ID: <20120627183757.GC23086@redhat.com> (raw)
In-Reply-To: <20120627183721.GA23086@redhat.com>
task_work_add() checks PF_EXITING to ensure it can't insert the new
twork after exit_task_work(). This means that the exiting task can
not use it after exit_signals().
Change task_work_add() and task_work_run() to use the fake
TWORK_EXITED pointer to synchronize with each other, now we can
move exit_task_work() down and make task_work_add() more useful.
Unfortunately, this means that the exiting task needs to take
pi_lock unconditionally.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
---
include/linux/task_work.h | 6 ++----
kernel/task_work.c | 15 ++++++++-------
2 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/include/linux/task_work.h b/include/linux/task_work.h
index 03640fb..ef70b01 100644
--- a/include/linux/task_work.h
+++ b/include/linux/task_work.h
@@ -1,9 +1,8 @@
#ifndef _LINUX_TASK_WORK_H
#define _LINUX_TASK_WORK_H
-#include <linux/sched.h>
-
struct task_work;
+struct task_struct;
typedef void (*task_work_func_t)(struct task_work *);
struct task_work {
@@ -25,8 +24,7 @@ void task_work_run(void);
static inline void exit_task_work(struct task_struct *task)
{
- if (unlikely(task->last_twork))
- task_work_run();
+ task_work_run();
}
#endif /* _LINUX_TASK_WORK_H */
diff --git a/kernel/task_work.c b/kernel/task_work.c
index a0a3133..b2ff3b7 100644
--- a/kernel/task_work.c
+++ b/kernel/task_work.c
@@ -6,6 +6,8 @@
* task->last_twork points to the last node in the circular single-linked list.
*/
+#define TWORK_EXITED ((struct task_work *)1)
+
int
task_work_add(struct task_struct *task, struct task_work *twork, bool notify)
{
@@ -18,12 +20,11 @@ task_work_add(struct task_struct *task, struct task_work *twork, bool notify)
return -ENOTSUPP;
#endif
/*
- * We must not insert the new work if the task has already passed
- * exit_task_work(). We rely on do_exit()->raw_spin_unlock_wait()
- * and check PF_EXITING under pi_lock.
+ * We must not insert the new work if the exiting task has already
+ * passed task_work_run().
*/
raw_spin_lock_irqsave(&task->pi_lock, flags);
- if (likely(!(task->flags & PF_EXITING))) {
+ if (likely(task->last_twork != TWORK_EXITED)) {
last = task->last_twork ?: twork;
task->last_twork = twork;
twork->next = last->next;
@@ -46,7 +47,7 @@ task_work_cancel(struct task_struct *task, task_work_func_t func)
raw_spin_lock_irqsave(&task->pi_lock, flags);
last = task->last_twork;
- if (last) {
+ if (last && last != TWORK_EXITED) {
twork = last;
do {
prev = twork;
@@ -77,10 +78,10 @@ void task_work_run(void)
raw_spin_lock_irq(&task->pi_lock);
last = task->last_twork;
- task->last_twork = NULL;
+ task->last_twork = (task->flags & PF_EXITING) ? TWORK_EXITED : NULL;
raw_spin_unlock_irq(&task->pi_lock);
- if (unlikely(!last))
+ if (!last)
return;
next = last->next;
--
1.5.5.1
next prev parent reply other threads:[~2012-06-27 18:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 12:44 deferring __fput() Mimi Zohar
2012-06-23 9:20 ` Al Viro
2012-06-23 19:45 ` Al Viro
2012-06-23 20:38 ` Oleg Nesterov
2012-06-23 21:01 ` Al Viro
2012-06-23 21:11 ` Al Viro
2012-06-24 4:16 ` Al Viro
2012-06-24 10:09 ` Al Viro
2012-06-24 16:54 ` Oleg Nesterov
2012-06-24 15:33 ` Oleg Nesterov
2012-06-25 6:03 ` Al Viro
2012-06-25 15:18 ` Oleg Nesterov
2012-06-27 18:37 ` [PATCH 0/4] Was: " Oleg Nesterov
2012-06-27 18:37 ` [PATCH 1/4] task_work: use the single-linked list to shrink sizeof(task_work) Oleg Nesterov
2012-06-27 18:37 ` Oleg Nesterov [this message]
2012-06-27 18:38 ` [PATCH 3/4] task_work: deal with task_work callbacks adding more work Oleg Nesterov
2012-06-27 18:38 ` [PATCH 4/4] task_work: kill task_work->data Oleg Nesterov
2012-06-27 19:05 ` Oleg Nesterov
2012-06-28 4:38 ` [PATCH 0/4] Was: deferring __fput() Al Viro
2012-06-28 16:22 ` Oleg Nesterov
2012-06-28 16:45 ` Oleg Nesterov
2012-06-30 6:24 ` Al Viro
2012-06-30 17:41 ` Oleg Nesterov
2012-06-29 5:30 ` Mimi Zohar
2012-06-29 8:33 ` Al Viro
2012-06-29 13:02 ` Mimi Zohar
2012-06-29 17:41 ` Al Viro
2012-06-29 21:38 ` Mimi Zohar
2012-06-29 23:56 ` Mimi Zohar
2012-06-30 5:02 ` Al Viro
2012-07-01 19:50 ` Mimi Zohar
2012-07-01 20:57 ` Al Viro
2012-07-02 1:46 ` Mimi Zohar
2012-07-02 3:43 ` Al Viro
2012-07-02 5:11 ` Al Viro
2012-07-02 11:49 ` Mimi Zohar
2012-07-02 12:02 ` Al Viro
2012-07-02 13:01 ` Mimi Zohar
2012-07-02 13:33 ` Al Viro
2012-07-02 14:50 ` Mimi Zohar
2012-08-21 13:05 ` [PATCH] task_work: add a scheduling point in task_work_run() Eric Dumazet
2012-08-21 20:37 ` Mimi Zohar
2012-08-21 21:32 ` Eric Dumazet
2012-08-22 3:13 ` Mimi Zohar
2012-08-22 5:27 ` Michael Wang
2012-08-22 5:38 ` Al Viro
2012-06-23 20:57 ` deferring __fput() Al Viro
2012-06-23 21:33 ` Al Viro
2012-06-24 15:20 ` Oleg Nesterov
2012-06-24 18:11 ` Oleg Nesterov
2012-06-25 12:03 ` Peter Zijlstra
2012-06-25 12:14 ` Al Viro
2012-06-25 13:19 ` Peter Zijlstra
2012-06-25 13:53 ` Al Viro
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=20120627183757.GC23086@redhat.com \
--to=oleg@redhat.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=zohar@linux.vnet.ibm.com \
/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).