From: Oleg Nesterov <oleg@tv-sign.ru>
To: Roland McGrath <roland@redhat.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Davide Libenzi <davidel@xmailserver.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] fix missed SIGCONT cases
Date: Fri, 29 Feb 2008 16:20:30 +0300 [thread overview]
Message-ID: <20080229132030.GA2301@tv-sign.ru> (raw)
In-Reply-To: <20080229120101.GA1410@tv-sign.ru>
On 02/29, Oleg Nesterov wrote:
>
> On 02/28, Roland McGrath wrote:
> >
> > I don't dislike the direction of your flag-setting approach above. But
> > it does introduce more new subtleties that warrant more thought.
>
> Yes sure.
Still. The more I think about it, the more I like it. It is so simple,
and allows us to do further cleanups. Please look at the patch below.
Now we don't need tasklist to send the signal.
handle_stop_signal() should be cleanuped as you pointed out, but this
patch only does the requied minimum.
I am worried about ptrace, but hopefully there is no problem.
Oleg.
--- 25/include/linux/sched.h~SIG_NP 2008-02-25 19:13:05.000000000 +0300
+++ 25/include/linux/sched.h 2008-02-29 15:38:00.000000000 +0300
@@ -455,6 +455,8 @@ struct signal_struct {
int group_stop_count;
unsigned int flags; /* see SIGNAL_* flags below */
+ unsigned int notify_parent; /* will be moved into ->flags */
+
/* POSIX.1b Interval Timers */
struct list_head posix_timers;
--- 25/kernel/signal.c~SIG_NP 2008-02-29 15:28:28.000000000 +0300
+++ 25/kernel/signal.c 2008-02-29 15:54:54.000000000 +0300
@@ -597,9 +597,7 @@ static void handle_stop_signal(int sig,
*/
p->signal->group_stop_count = 0;
p->signal->flags = SIGNAL_STOP_CONTINUED;
- spin_unlock(&p->sighand->siglock);
- do_notify_parent_cldstop(p, CLD_STOPPED);
- spin_lock(&p->sighand->siglock);
+ p->signal->notify_parent = CLD_STOPPED;
}
rm_from_queue(SIG_KERNEL_STOP_MASK, &p->signal->shared_pending);
t = p;
@@ -638,9 +636,7 @@ static void handle_stop_signal(int sig,
*/
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);
+ p->signal->notify_parent = CLD_CONTINUED;
} else {
/*
* We are not stopped, but there could be a stop
@@ -1748,6 +1744,21 @@ static int do_signal_stop(int signr)
return 1;
}
+static int handle_notify_parent(void)
+{
+ int why = current->signal->notify_parent;
+ if (likely(!why))
+ return 0;
+ current->signal->notify_parent = 0;
+ spin_unlock_irq(¤t->sighand->siglock);
+
+ read_lock(&tasklist_lock);
+ do_notify_parent_cldstop(current, why);
+ read_unlock(&tasklist_lock);
+
+ return 1;
+}
+
int get_signal_to_deliver(siginfo_t *info, struct k_sigaction *return_ka,
struct pt_regs *regs, void *cookie)
{
@@ -1761,6 +1772,9 @@ relock:
for (;;) {
struct k_sigaction *ka;
+ if (unlikely(handle_notify_parent()))
+ goto relock;
+
if (unlikely(current->signal->group_stop_count > 0) &&
do_signal_stop(0))
goto relock;
next prev parent reply other threads:[~2008-02-29 13:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 15:22 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 ` [PATCH] handle_stop_signal: don't wake up the stopped task until it sees SIGCONT Oleg Nesterov
2008-02-28 16:56 ` 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 [this message]
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=20080229132030.GA2301@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®