The functions remquo(), remquof() and remquol() are thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions pthread_attr_setstacksize() and
pthread_attr_getstacksize() are thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The functions pthread_attr_setstackaddr() and
pthread_attr_getstackaddr() are thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The naming convention shown in the page was ancient.
Now, the page is consistent with Documentation/devices.txt
(where it is noted that "The use of the capital letters
D, H and E for the 3.5" models have been deprecated, since
the drive type is insignificant for these devices"
Reported-by: Sam Varshavchik <mrsam@courier-mta.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The current text reflects the general worry in the kernel about
recipients of O_PATH fds being able to hardlink the referenced
files. It turns out that it was possible to link these files
regardless of any possible security concerns.
Linux 3.11 removes the capability check in AT_EMPTY_PATH.
I expect that this functionality will be generally useful,
so let's document it better.
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Linux commit 3ee6dafc677a68e461a7ddafc94a580ebab80735 caused
remap_file_pages to be emulated when used on real file.
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
create_module(), delete_module(), init_module(), and
query_module() are not declared in header files, but
through an accident of history glibc provides an ABI
for them that it continues to maintain, for
compatibility reasons.
Reported-by: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Note the use of fanotify_mark() 'event_f_flags' to control
the file status flags for the file descriptors returned via
'fanotify_event_metadata.fd'.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
* Using large buffer sizes for read(2) is orthogonal to the
discussion of variable-length event structures.
* Move the discussion of the read() return value to follow
discussion of what the read() actually returns in its buffer.
* Related rewordings.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Update as per http://www.spinics.net/lists/linux-man/msg05624.html
where Jan Kara proposed to clarify the deletion of events from the
fanotify queue and the occurrence of ENOENT when writing to the
fanotify file descriptor.
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk