All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: "David S. Miller" <davem@redhat.com>
Cc: akpm@osdl.org, linux-arch@vger.kernel.org, roland@redhat.com
Subject: Re: signal-race-fix.patch
Date: Fri, 19 Mar 2004 17:37:39 -0600	[thread overview]
Message-ID: <405B8443.40701@acm.org> (raw)
In-Reply-To: <20040319152821.3c306ccc.davem@redhat.com>

David S. Miller wrote:

>On Fri, 19 Mar 2004 16:42:03 -0600
>Corey Minyard <minyard@acm.org> wrote:
>
>  
>
>>BTW, here is a new patch that covers that problem.
>>    
>>
>
>Ok, I'll cook up the sparc bits.
>
>Although I can just see someone updating something in the 'ka' and
>expecting it to take effect, then spending a serious amount of time
>debugging only to find it's a pointer to a stack local copy of the
>info.
>
>:-)
>  
>
True.  I should probably rename the variable to ka_copy, or something 
like that to avoid somebody using it.  It actually happens in another 
place in the code, too, on x86.  There is a situation in setup_frame() 
and setup_rt_frame() where if it cannot write the signal frame to the 
stack, it sets the handler to SIG_DFL if it is a SEGV.

I'm not sure what to do about that one yet.

-Corey

  reply	other threads:[~2004-03-19 23:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 20:01 signal-race-fix.patch Andrew Morton
2004-03-19 22:12 ` signal-race-fix.patch David S. Miller
2004-03-19 22:38   ` signal-race-fix.patch Corey Minyard
2004-03-19 22:42   ` signal-race-fix.patch Corey Minyard
2004-03-19 23:28     ` signal-race-fix.patch David S. Miller
2004-03-19 23:37       ` Corey Minyard [this message]
2004-03-19 23:49     ` signal-race-fix.patch David S. Miller
2004-03-20  0:10       ` signal-race-fix.patch Corey Minyard
2004-03-23 10:20         ` signal-race-fix.patch Andrew Morton
2004-03-23 18:43           ` signal-race-fix.patch David S. Miller
2004-03-23 19:35           ` signal-race-fix.patch Roland McGrath
2004-03-23 20:18             ` signal-race-fix.patch David S. Miller
2004-03-24  1:54           ` signal-race-fix.patch David Mosberger
2004-03-24  3:58             ` signal-race-fix.patch Roland McGrath
2004-03-24  6:59               ` signal-race-fix.patch David Mosberger
2004-03-24 21:53           ` signal-race-fix.patch David Mosberger
2004-03-25  0:31             ` signal-race-fix.patch Arun Sharma
2004-07-26 21:17           ` signal-race-fix.patch Corey Minyard
2004-07-26 21:22             ` signal-race-fix.patch Andrew Morton
2004-07-27  3:40               ` signal-race-fix.patch Corey Minyard
2004-07-27  4:57                 ` signal-race-fix.patch Andrew Morton
2004-03-20  0:46       ` signal-race-fix.patch 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=405B8443.40701@acm.org \
    --to=minyard@acm.org \
    --cc=akpm@osdl.org \
    --cc=davem@redhat.com \
    --cc=linux-arch@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 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.