summaryrefslogtreecommitdiff
path: root/fs/notify
diff options
context:
space:
mode:
authorNathan Lynch <ntl@pobox.com>2010-08-10 18:03:08 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2010-08-11 08:59:20 -0700
commita2a20c412c86e0bb46a9ab0dd31bcfe6d201b913 (patch)
tree25d32209eab03f3e3aa5eca7a93e5199174abb5a /fs/notify
parentc7e49c1488ab20342eaaf38f1ca35a207f4c051d (diff)
downloadlinux-3.10-a2a20c412c86e0bb46a9ab0dd31bcfe6d201b913.tar.gz
linux-3.10-a2a20c412c86e0bb46a9ab0dd31bcfe6d201b913.tar.bz2
linux-3.10-a2a20c412c86e0bb46a9ab0dd31bcfe6d201b913.zip
signalfd: fill in ssi_int for posix timers and message queues
If signalfd is used to consume a signal generated by a POSIX interval timer or POSIX message queue, the ssi_int field does not reflect the data (sigevent->sigev_value) supplied to timer_create(2) or mq_notify(3). (The ssi_ptr field, however, is filled in.) This behavior differs from signalfd's treatment of sigqueue-generated signals -- see the default case in signalfd_copyinfo. It also gives results that differ from the case when a signal is handled conventionally via a sigaction-registered handler. So, set signalfd_siginfo->ssi_int in the remaining cases (__SI_TIMER, __SI_MESGQ) where ssi_ptr is set. akpm: a non-back-compatible change. Merge into -stable to minimise the number of kernels which are in the field and which miss this feature. Signed-off-by: Nathan Lynch <ntl@pobox.com> Acked-by: Davide Libenzi <davidel@xmailserver.org> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/notify')
0 files changed, 0 insertions, 0 deletions