From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Blaisorblade <blaisorblade_spam@yahoo.it>,
dopez <lists@dopez.xs4all.nl>
Subject: Re: [uml-devel] Re: 2.6.9-bb3 creates zombie threads in SKAS
Date: Tue, 30 Nov 2004 20:23:40 +0100 [thread overview]
Message-ID: <41ACC8BC.6050507@fujitsu-siemens.com> (raw)
In-Reply-To: <241401c4d70e$38b53450$0201a8c0@hawk>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Christopher S. Aker wrote:
> I've been able to narrow this down to the "signal-delivery" patch. 2.6.10-rc2-mm3
> without the patch is fine, whereas adding the signal-delivery patch and you'll get
> mysql zombies inside the UML. This happens on a variety of hosts, including
> 2.6.10-rc2-bk7 + skas-v7.
>
> I just noticed 2.6.10-rc2-mm4 is out, and the patch there is named
> "uml-redo-the-signal-delivery-mechanism.patch".
>
> -Chris
>
Have found a bug in the signal-delivery patch a few days ago.
Could you please try the appended patch? (It's relevant for usage of RTSIGs
only, don't know, whether this could help you)
Bodo
[-- Attachment #2: extramask.patch --]
[-- Type: text/x-diff, Size: 1287 bytes --]
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Restoring of current->blocked in sys_sigreturn is wrong.
The first (long ) of the mask correctly is fetched from sc->oldmask.
The further longs again come from there, but correctly should be
taken from frame->extramask.
Signed-off-by: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
---
diff -puN arch/um/sys-i386/signal.c~extramask arch/um/sys-i386/signal.c
--- linux-2.6.10-rc2/arch/um/sys-i386/signal.c~extramask 2004-11-26 14:03:10.770096974 +0100
+++ linux-2.6.10-rc2-root/arch/um/sys-i386/signal.c 2004-11-26 14:11:03.264403385 +0100
@@ -307,11 +307,12 @@ long sys_sigreturn(struct pt_regs regs)
struct sigframe __user *frame = (struct sigframe *)(sp - 8);
sigset_t set;
struct sigcontext __user *sc = &frame->sc;
- unsigned long __user *mask = &sc->oldmask;
+ unsigned long __user *oldmask = &sc->oldmask;
+ unsigned long __user *extramask = &frame->extramask;
int sig_size = (_NSIG_WORDS - 1) * sizeof(unsigned long);
- if(copy_from_user(&set.sig[0], mask, sizeof(&set.sig[0])) ||
- copy_from_user(&set.sig[1], mask, sig_size))
+ if(copy_from_user(&set.sig[0], oldmask, sizeof(&set.sig[0])) ||
+ copy_from_user(&set.sig[1], extramask, sig_size))
goto segfault;
sigdelsetmask(&set, ~_BLOCKABLE);
_
next prev parent reply other threads:[~2004-11-30 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000901c4d0e1$e7f998d0$0201a8c0@hawk>
2004-11-22 22:46 ` [uml-devel] Re: 2.6.9-bb3 creates zombie threads in SKAS Blaisorblade
2004-11-22 23:33 ` Christopher S. Aker
2004-11-22 23:56 ` roland
2004-11-23 7:28 ` [uml-devel] Updated token-limiter patch, was " Christopher S. Aker
2004-11-23 20:10 ` Blaisorblade
2004-11-23 14:48 ` [uml-devel] " Bodo Stroesser
2004-11-23 17:49 ` Christopher S. Aker
2004-11-23 17:53 ` dopez
2004-11-23 19:30 ` Blaisorblade
2004-11-23 18:22 ` Blaisorblade
2004-11-23 18:29 ` Christopher S. Aker
2004-11-30 18:55 ` Christopher S. Aker
2004-11-30 19:23 ` Bodo Stroesser [this message]
2004-11-30 20:59 ` Christopher S. Aker
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=41ACC8BC.6050507@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=caker@theshore.net \
--cc=lists@dopez.xs4all.nl \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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