From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Anton Blanchard <anton@samba.org>, Andrew Morton <akpm@digeo.com>,
Arjan van de Ven <arjanv@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: heavy handed exit() in latest BK
Date: Sun, 9 Feb 2003 13:09:26 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0302091307510.5085-100000@localhost.localdomain> (raw)
In-Reply-To: <200302091156.h19BuoH07869@magilla.sf.frob.com>
On Sun, 9 Feb 2003, Roland McGrath wrote:
> > - a read_lock(&tasklist_lock) is missing around the group_send_sig_info()
> > in send_sig_info().
>
> Indeed. I still intend to clean up those entry points and haven't
> gotten to it, so I hadn't bothered with this yet either (though I think
> I sent it to you for the backport). It certainly does bite in practice,
> e.g. SIGPIPE.
it does bite - here's the correctness fix meanwhile, until the interface
is cleaned up.
Ingo
--- linux/kernel/signal.c.orig
+++ linux/kernel/signal.c
@@ -1083,17 +1083,19 @@
int
send_sig_info(int sig, struct siginfo *info, struct task_struct *p)
{
+ int ret;
+
/* XXX should nix these interfaces and update the kernel */
- if (T(sig, SIG_KERNEL_BROADCAST_MASK))
- /* XXX do callers really always hold the tasklist_lock?? */
- return group_send_sig_info(sig, info, p);
- else {
- int error;
+ if (T(sig, SIG_KERNEL_BROADCAST_MASK)) {
+ read_lock(&tasklist_lock);
+ ret = group_send_sig_info(sig, info, p);
+ read_unlock(&tasklist_lock);
+ } else {
spin_lock_irq(&p->sighand->siglock);
- error = specific_send_sig_info(sig, info, p);
+ ret = specific_send_sig_info(sig, info, p);
spin_unlock_irq(&p->sighand->siglock);
- return error;
}
+ return ret;
}
int
next prev parent reply other threads:[~2003-02-09 11:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302091130.h19BU2107744@magilla.sf.frob.com>
2003-02-09 11:40 ` heavy handed exit() in latest BK Ingo Molnar
2003-02-09 11:56 ` Roland McGrath
2003-02-09 12:09 ` Ingo Molnar [this message]
2003-02-09 12:18 ` Ingo Molnar
2003-02-09 12:23 ` Ingo Molnar
2003-02-09 12:22 ` Arjan van de Ven
2003-02-10 1:07 ` Linus Torvalds
2003-02-10 1:27 ` Roland McGrath
2003-02-09 0:57 Anton Blanchard
2003-02-09 2:00 ` Linus Torvalds
2003-02-09 2:17 ` Roland McGrath
2003-02-09 2:19 ` Linus Torvalds
2003-02-09 2:31 ` Roland McGrath
2003-02-09 2:34 ` Linus Torvalds
2003-02-09 2:33 ` Linus Torvalds
2003-02-09 2:41 ` Roland McGrath
2003-02-09 3:30 ` Roland McGrath
2003-02-09 3:33 ` Roland McGrath
2003-02-09 3:37 ` Linus Torvalds
2003-02-09 3:40 ` Linus Torvalds
2003-02-09 3:48 ` Roland McGrath
2003-02-09 4:51 ` Linus Torvalds
2003-02-09 4:57 ` Linus Torvalds
2003-02-09 5:00 ` Roland McGrath
2003-02-09 9:28 ` Russell King
2003-02-10 8:53 ` Ingo Molnar
2003-02-10 15:22 ` Linus Torvalds
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=Pine.LNX.4.44.0302091307510.5085-100000@localhost.localdomain \
--to=mingo@elte.hu \
--cc=akpm@digeo.com \
--cc=anton@samba.org \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@transmeta.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).