Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)

On Wed, 2007-06-06 at 22:20 -0400, Jeff Dike wrote:
> On Thu, Jun 07, 2007 at 08:43:42AM +1000, Paul Mackerras wrote:
> > What Ben was talking about was stealing a synchronous SEGV from a task
> > without stopping it, and as Ben says that makes no sense.
> > Intercepting a signal and stopping the task is reasonable, and that is
> > what ptrace does, and I assume also UML.
> 
> It is, but I can also see UML stealing the SEGV from the child.  The
> UML skas does this - a ptrace extension, PTRACE_FAULTINFO, is used to
> extract page fault information from the child, and other pieces of the
> patch are used to fix the fault without the child continuing until
> it's fixed.  So, in this case, the child never sees the SEGV.

But you use ptrace and don't steal signals with dequeue_signal() on a
live other task, which is ok.

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
    • From: Jeff Dike <[email protected]>

• References:
  • Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes
    • From: Nicholas Miell <[email protected]>
  • Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes
    • From: Benjamin Herrenschmidt <[email protected]>
  • Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes
    • From: Nicholas Miell <[email protected]>
  • Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes
    • From: Davide Libenzi <[email protected]>
  • Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes
    • From: Nicholas Miell <[email protected]>
  • Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes
    • From: Davide Libenzi <[email protected]>
  • signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
    • From: Nicholas Miell <[email protected]>
  • Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
    • From: Benjamin Herrenschmidt <[email protected]>
  • Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
    • From: Jeff Dike <[email protected]>
  • Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
    • From: Paul Mackerras <[email protected]>
  • Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
    • From: Jeff Dike <[email protected]>

• Prev by Date: Re: [BUG] ptraced process waiting on syscall may return kernel internal errnos
• Next by Date: [PATCH] enable interrupts in user path of page fault.
• Previous by thread: Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
• Next by thread: Re: signalfd API issues (was Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]