mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: ak@muc.de, drepper@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Support TIF_RESTORE_SIGMASK on x86_64
Date: Mon, 03 Jul 2006 11:39:31 +0100	[thread overview]
Message-ID: <1151923171.12290.6.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060703031937.274aa506.akpm@osdl.org>

On Mon, 2006-07-03 at 03:19 -0700, Andrew Morton wrote:
> Could you please describe the signal mask fix? 

@@ -583,7 +583,7 @@
        if (!user_mode(regs))
                return;

-       if (!test_thread_flag(TIF_RESTORE_SIGMASK))
+       if (test_thread_flag(TIF_RESTORE_SIGMASK))
                oldset = &current->saved_sigmask;
        else
                oldset = &current->blocked;


>  Is that likely to have caused the above symptoms?

Yeah, it'll screw up the signal mask all over the place. 
cf. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180567
also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179228

> Should we be setting TASK_INTERRUPTIBLE before releasing that lock?

Before releasing current->sighand->siglock? Nah, schedule() will check
for pending signals -- it's not like racing with a wake_up() 

-- 
dwmw2


  reply	other threads:[~2006-07-03 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03  9:41 David Woodhouse
2006-07-03  9:47 ` [PATCH 2/2] pselect/ppoll support " David Woodhouse
2006-07-03 10:40   ` Andi Kleen
2006-07-03 10:19 ` [PATCH 1/2] Support TIF_RESTORE_SIGMASK " Andrew Morton
2006-07-03 10:39   ` David Woodhouse [this message]
2006-07-03 14:16   ` Ulrich Drepper

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=1151923171.12290.6.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®