[lkml]   [2009]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: F_SETOWN_TID: F_SETOWN was thread-specific for a while
On 08/10, stephane eranian wrote:
> You must use F_SETSIG on SIGIO if you want your signal handler to
> receive the file descriptor in siginfo. This is useful if you want to perform
> some actions on the descriptor. That is the case in perfmon and this is
> the case in certain situations with perfcounters as well.
> Setting SA_SIGINFO provides siginfo, but the si_fd field is NOT set
> correctly without F_SETSIG. I have verified this with perfcounters, and
> this is indeed the case.
> This behavior seems kind of odd to me.

Agreed, this looks a bit odd. But at least this is documented. From
man 2 fcntl:

By using F_SETSIG with a nonzero value, and setting SA_SIGINFO for the
signal handler (see sigac- tion(2)), extra information about I/O events
is passed to the handler in a siginfo_t structure. If the si_code
field indicates the source is SI_SIGIO, the si_fd field gives the file
descriptor associated with the event. Otherwise, there is no indication
which file descriptors are pending,

Not sure if it is safe to change the historical behaviour.

(the manpage is not exactly right though, and the comment in send_sigio_to_task()
is not right too: SI_SIGIO (and, btw, SI_QUEUE/SI_DETHREAD) is never used).


 \ /
  Last update: 2009-08-10 19:11    [W:0.101 / U:0.076 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site