linux-kernel - inotify SIGIO documentation for inotify.7 man page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 08 Apr 2008 00:16:09 +0200
From:	Michael Kerrisk <mtk.manpages@...glemail.com>
To:	Dmitry Antipov <antipov@....rtsoft.ru>
CC:	Robert Love <rlove@...gle.com>,
	John McCutchan <ttb@...tacle.dhs.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: inotify SIGIO documentation for inotify.7 man page

Hi Dmitry,

I don't think I got notification of the 2.6.25 API change to inotify from
you.  Please CC me on API changes.

The following is my attempt to document the SIGIO feature that is new in
2.6.25.  Does this look okay to you?

       Since Linux 2.6.25,  signal-driven  I/O  notification  is
       available  for  inotify file descriptors; see the discus-
       sion of F_SETFL (for setting the O_ASYNC flag), F_SETOWN,
       and   F_SETSIG  in  fcntl(2).   The  siginfo_t  structure
       (described in sigaction(2)) that is passed to the  signal
       handler has the following fields set: si_fd is set to the
       inotify file descriptor number; si_signo is  set  to  the
       signal  number;  si_code is set to POLL_IN; and POLLIN is
       set in si_band.

Cheers,

Michael

-- 
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/
Want to report a man-pages bug?  Look here:
http://www.kernel.org/doc/man-pages/reporting_bugs.html


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