All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Michael Cree <mcree@orcon.net.nz>
Cc: linux-alpha@vger.kernel.org
Subject: Re: Bug: retry of clone() on Alpha can result in zeroed process thread pointer
Date: Wed, 30 Jul 2014 07:56:02 -1000	[thread overview]
Message-ID: <53D931B2.4000709@twiddle.net> (raw)
In-Reply-To: <20140730045117.GD2262@stolen.phys.waikato.ac.nz>

On 07/29/2014 06:51 PM, Michael Cree wrote:
> On Tue, Jul 29, 2014 at 12:23:45PM -1000, Richard Henderson wrote:
>> I don't think this will help, but it's worth a test, prior to totally
>> re-writing entry.S.  There's a chance of confusion of the value of regs->r0 if
>> there is in fact no error.
> 
> No, it did not help.  The glibc nptl/tst-eintr3 test still occassionally
> sefgaults and that is occurring because rduniq returned a NULL pointer.

Another try.


r~



diff --git a/arch/alpha/kernel/signal.c b/arch/alpha/kernel/signal.c
index 6cec288..2d6c0e4 100644
--- a/arch/alpha/kernel/signal.c
+++ b/arch/alpha/kernel/signal.c
@@ -518,6 +518,7 @@ do_signal
                        case ERESTART_RESTARTBLOCK:
                                /* Set v0 to the restart_syscall and replay */
                                regs->r0 = __NR_restart_syscall;
+                               regs->r19 = r19;
                                regs->pc -= 4;
                                break;
                        }


  reply	other threads:[~2014-07-30 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  8:52 Bug: retry of clone() on Alpha can result in zeroed process thread pointer Michael Cree
2014-07-24 18:19 ` Richard Henderson
2014-07-24 19:30   ` Michael Cree
2014-07-29 22:23 ` Richard Henderson
2014-07-30  4:51   ` Michael Cree
2014-07-30 17:56     ` Richard Henderson [this message]
2014-07-30 19:30 ` Richard Henderson

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=53D931B2.4000709@twiddle.net \
    --to=rth@twiddle.net \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mcree@orcon.net.nz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.