Skip to content
Snippets Groups Projects
Select Git revision
  • nor-4.4
  • amp-v4.4
  • amp-v4.3
  • nor-4.3
  • amp-v3.14
  • master default
  • v4.1-rc2
  • v4.1-rc1
  • v4.0
  • v4.0-rc7
  • v4.0-rc6
  • v4.0-rc5
  • v4.0-rc4
  • v4.0-rc3
  • v4.0-rc2
  • v4.0-rc1
  • v3.19
  • v3.19-rc7
  • v3.19-rc6
  • v3.19-rc5
  • v3.19-rc4
  • v3.19-rc3
  • v3.19-rc2
  • v3.19-rc1
  • v3.18
  • v3.18-rc7
26 results

linux

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Davide Libenzi authored
    This simplifies signalfd code, by avoiding it to remain attached to the
    sighand during its lifetime.
    
    In this way, the signalfd remain attached to the sighand only during
    poll(2) (and select and epoll) and read(2).  This also allows to remove
    all the custom "tsk == current" checks in kernel/signal.c, since
    dequeue_signal() will only be called by "current".
    
    I think this is also what Ben was suggesting time ago.
    
    The external effect of this, is that a thread can extract only its own
    private signals and the group ones.  I think this is an acceptable
    behaviour, in that those are the signals the thread would be able to
    fetch w/out signalfd.
    
    Signed-off-by: default avatarDavide Libenzi <davidel@xmailserver.org>
    Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    b8fceee1
    History
    Name Last commit Last update