Inspection of the definition of CMSG_FIRSTHDR (both in glibc and
the suggested definition in RFC3542) shows that it yields the
msg_control field. So when sending, the pointer placed in
msg_control should be suitably aligned as a struct cmsghdr.
In the sending example, buf was declared as a bare char array,
and so is not necessarily suitably aligned.
The solution here involves placing buf inside a union, and is
based on the sockets/scm_rights_send.c sample from The Linux
Programming Interface "dist" source code collection.
Signed-off-by: David Wragg <david@wragg.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The current example code requires passing an absolute
path to the mount to be watched.
By passing AT_FDCWD to fanotify_mark it can use both
absolute and relative paths.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
In most other manpages file descriptors are called 'fd'.
This patches renames attribute 'd' to 'fd'.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
/proc/thread-self has been introduced in Linux 3.17 with
commit 0097875bd41528922fb3bb5f348c53f17e00e2fd.
Signed-off-by: Bernhard Walle <bernhard@bwalle.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Already documented in getgroups(2), but not in sysconf(3).
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Since credentials.7 discusses supplementary GIDs, it should reference
getgroups(2).
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
locale(5) describes what a locale should define but doesn't
spell out how (in what format). The patch attempts to address
this, it also has few trivial additional enhancements.
* Reference to locale(7) for category descriptions.
* Clarify first_workday in NOTES a bit.
* Add upstream BZ reference for two missing LC_ADDRESS fields.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
As noted by Siddhesh:
The ld.so man page says:
$ORIGIN (or equivalently ${ORIGIN})
This expands to the directory containing the
application executable. Thus, an application located
in somedir/app could be compiled with
This is incorrect since it expands to the directory containing
the DSO and not the application executable. This seems like
deliberate behaviour in dl-object.c, so it needs to be fixed in
the man page.
See http://stackoverflow.com/questions/26280738/what-is-the-equivalent-of-loader-path-for-rpath-specification-on-linux/26281226#26281226
Reported-by: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The size of the process name has always been at most 16 byte
_including_ the null terminator. This also means that the
name returned by PR_GET_NAME is always null-terminated.
Signed-off-by: Andreas Schwab <schwab@suse.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Unfortunately, fanotify does not inform listeners for all paths
under which a touched filesystem object is visible, but only the
listener using the same path as the process touching the
filesystem object.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Calling fallocate(2) does not result in inotify events.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
fallocate(2) should create FAN_MODIFY events but does not.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
I bumped the Linux version number in the BUGS section to 3.17.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Manuel López-Ibáñez