From: Oleg Nesterov <oleg@tv-sign.ru>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Roland McGrath <roland@redhat.com>,
Davide Libenzi <davidel@xmailserver.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH] handle_stop_signal: don't wake up the stopped task until it sees SIGCONT
Date: Thu, 28 Feb 2008 19:45:29 +0300 [thread overview]
Message-ID: <20080228164529.GA12695@tv-sign.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0802281711500.3391@jikos.suse.cz>
On 02/28, Jiri Kosina wrote:
>
> On Thu, 28 Feb 2008, Oleg Nesterov wrote:
>
> > Hmm... Can't we make a simpler patch for the start? See below.
> > We can notify the parent earlier, before waking the TASK_STOPPED
> > child. This should fix this race, no?
>
> Yes, this looks also like a correct fix to me (haven't tried to run the
> actual test yet, but 'obviously' it should close the race).
Thanks, please ack this patch unless you have any objections.
I tested this patch with Jiri's test-case, seems to work.
The Roland's review is still needed ;)
-------------------------------------------------------------------------------
[PATCH] handle_stop_signal: don't wake up the stopped task until it sees SIGCONT
The bug was found by Jiri Kosina <jkosina@suse.cz>, and the patch is based
on his ideas.
handle_stop_signal(SIGCONT) wakes up the stopped task and unlocks ->siglock
for do_notify_parent_cldstop(p, CLD_CONTINUED). The woken task returns from
do_signal_stop(), takes ->siglock and resumes to user-space without actually
seeing SIGCONT which may have a handler.
Move the code realated to do_notify_parent_cldstop(CLD_CONTINUED) up, before
"wake_up_state(t, state)".
NOTE: It is possible that the subsequent rm_from_queue(SIG_KERNEL_STOP_MASK)
removes SIGSTOP which comes after SIGCONT when we drop ->siglock. Not nice,
but possible even without this change. Hopefully we can remove the parent
notifying code from the sender path completely, but this needs more thinking.
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
--- 25/kernel/signal.c~HSS_SIGCONT_RACE 2008-02-28 19:22:32.000000000 +0300
+++ 25/kernel/signal.c 2008-02-28 19:27:52.000000000 +0300
@@ -601,12 +601,31 @@ static void handle_stop_signal(int sig,
do_notify_parent_cldstop(p, CLD_STOPPED);
spin_lock(&p->sighand->siglock);
}
+
+ if (p->signal->flags & SIGNAL_STOP_STOPPED) {
+ /*
+ * We were in fact stopped, and are now continued.
+ * Notify the parent with CLD_CONTINUED.
+ */
+ p->signal->flags = SIGNAL_STOP_CONTINUED;
+ p->signal->group_exit_code = 0;
+ spin_unlock(&p->sighand->siglock);
+ do_notify_parent_cldstop(p, CLD_CONTINUED);
+ spin_lock(&p->sighand->siglock);
+ } else {
+ /*
+ * We are not stopped, but there could be a stop
+ * signal in the middle of being processed after
+ * being removed from the queue. Clear that too.
+ */
+ p->signal->flags = 0;
+ }
+
rm_from_queue(SIG_KERNEL_STOP_MASK, &p->signal->shared_pending);
t = p;
do {
unsigned int state;
rm_from_queue(SIG_KERNEL_STOP_MASK, &t->pending);
-
/*
* If there is a handler for SIGCONT, we must make
* sure that no thread returns to user mode before
@@ -630,25 +649,6 @@ static void handle_stop_signal(int sig,
t = next_thread(t);
} while (t != p);
-
- if (p->signal->flags & SIGNAL_STOP_STOPPED) {
- /*
- * We were in fact stopped, and are now continued.
- * Notify the parent with CLD_CONTINUED.
- */
- p->signal->flags = SIGNAL_STOP_CONTINUED;
- p->signal->group_exit_code = 0;
- spin_unlock(&p->sighand->siglock);
- do_notify_parent_cldstop(p, CLD_CONTINUED);
- spin_lock(&p->sighand->siglock);
- } else {
- /*
- * We are not stopped, but there could be a stop
- * signal in the middle of being processed after
- * being removed from the queue. Clear that too.
- */
- p->signal->flags = 0;
- }
} else if (sig == SIGKILL) {
/*
* Make sure that any pending stop signal already dequeued
next prev parent reply other threads:[~2008-02-28 16:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 15:22 [PATCH] [RFC] fix missed SIGCONT cases Jiri Kosina
2008-02-27 21:00 ` Roland McGrath
2008-02-27 22:04 ` Jiri Kosina
2008-02-28 10:26 ` Roland McGrath
2008-02-28 11:42 ` Jiri Kosina
2008-02-28 15:32 ` Oleg Nesterov
2008-02-28 15:32 ` Jiri Kosina
2008-02-28 15:30 ` Oleg Nesterov
2008-02-28 15:40 ` Jiri Kosina
2008-02-28 16:08 ` Oleg Nesterov
2008-02-28 16:13 ` Jiri Kosina
2008-02-28 16:45 ` Oleg Nesterov [this message]
2008-02-28 16:56 ` [PATCH] handle_stop_signal: don't wake up the stopped task until it sees SIGCONT Jiri Kosina
2008-02-29 2:39 ` [PATCH] [RFC] fix missed SIGCONT cases Roland McGrath
2008-02-29 12:01 ` Oleg Nesterov
2008-02-29 13:20 ` Oleg Nesterov
2008-03-01 1:59 ` Roland McGrath
2008-03-01 16:41 ` Oleg Nesterov
2008-03-03 13:25 ` Oleg Nesterov
2008-03-06 10:50 ` Roland McGrath
2008-03-06 9:05 ` Roland McGrath
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=20080228164529.GA12695@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.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
all inboxes | Powered by JetHome®