arch_prctl.2, execveat.2, fanotify_mark.2, fcntl.2, fork.2, madvise.2, mknod.2, mmap.2, modify_ldt.2, mount.2, open.2, prctl.2, ptrace.2, restart_syscall.2, seccomp.2, semop.2, set_thread_area.2, symlink.2, umount.2, unlink.2, error.3, getnetent.3, getprotoent.3, getservent.3, getutent.3, glob.3, login.3, setjmp.3, setnetgrent.3, wordexp.3, epoll.7: Remove section number from page self reference

Fix places where pages refer to the function that they describe
and include a section number in that reference. Such references
cause some HTML-rendering tools to create self-references in the
page.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/arch_prctl.2

@@ -115,7 +115,7 @@ is disabled in some kernels.
 
 Context switches for 64-bit segment bases are rather expensive.
 As an optimization, if a 32-bit TLS base address is used,
-.BR arch_prctl (2)
+.BR arch_prctl ()
 may use a real TLS entry as if
 .BR set_thread_area (2)
 had been called, instead of manipulating the segment base register directly.
@@ -126,7 +126,7 @@ with the
 flag.
 
 Because of the aforementioned optimization, using
-.BR arch_prctl (2)
+.BR arch_prctl ()
 and
 .BR set_thread_area (2)
 in the same thread is dangerous, as they may overwrite each other's

man2/execveat.2

@@ -203,7 +203,7 @@ is the value given in
 For the same reasons described in
 .BR fexecve (3),
 the natural idiom when using
-.BR execveat (2)
+.BR execveat ()
 is to set the close-on-exec flag on
 .IR dirfd .
 (But see BUGS.)

man2/fanotify_mark.2

@@ -37,7 +37,7 @@ object
 For an overview of the fanotify API, see
 .BR fanotify (7).
 .PP
-.BR fanotify_mark (2)
+.BR fanotify_mark ()
 adds, removes, or modifies an fanotify mark on a filesystem object.
 The caller must have read permission on the filesystem object that
 is to be marked.
@@ -323,7 +323,7 @@ event.
 .IP *
 .\" Fixed by commit cc299a98eb13a9853675a9cbb90b30b4011e1406
 If
-.BR fanotify_mark (2)
+.BR fanotify_mark ()
 is called with
 .BR FAN_MARK_FLUSH ,
 .I flags

man2/fcntl.2

@@ -513,7 +513,7 @@ Open file description locks placed via the same open file description
 or via a duplicate of the file descriptor created by
 .BR fork (2),
 .BR dup (2),
-.BR fcntl (2)
+.BR fcntl ()
 .BR F_DUPFD ,
 and so on) are always compatible:
 if a new lock is placed on an already locked region,
@@ -1348,7 +1348,7 @@ Currently, only the
 .I tmpfs
 filesystem supports sealing.
 On other filesystems, all
-.BR fcntl (2)
+.BR fcntl ()
 operations that operate on seals will return
 .BR EINVAL .
 
@@ -1389,7 +1389,7 @@ The following seals are available:
 .TP
 .BR F_SEAL_SEAL
 If this seal is set, any further call to
-.BR fcntl (2)
+.BR fcntl ()
 with
 .B F_ADD_SEALS
 will fail with

man2/fork.2

@@ -162,7 +162,7 @@ and other pthreads objects; the use of
 may be helpful for dealing with problems that this can cause.
 .IP *
 After a
-.BR fork (2)
+.BR fork ()
 in a multithreaded program,
 the child can safely call only async-signal-safe functions (see
 .BR signal (7))

man2/madvise.2

@@ -505,7 +505,7 @@ and so on, with behavior close to the similarly named flags listed above.
 (POSIX.1-2008 adds a further flag,
 .BR POSIX_MADV_NOREUSE ,
 that has no analog in
-.BR madvise (2).)
+.BR madvise ().)
 .SH NOTES
 .SS Linux notes
 The Linux implementation requires that the address

man2/mknod.2

@@ -115,7 +115,7 @@ otherwise it will be owned by the effective group ID of the process.
 The
 .BR mknodat ()
 system call operates in exactly the same way as
-.BR mknod (2),
+.BR mknod (),
 except for the differences described here.
 
 If the pathname given in
@@ -125,7 +125,7 @@ referred to by the file descriptor
 .I dirfd
 (rather than relative to the current working directory of
 the calling process, as is done by
-.BR mknod (2)
+.BR mknod ()
 for a relative pathname).
 
 If
@@ -138,7 +138,7 @@ then
 .I pathname
 is interpreted relative to the current working
 directory of the calling process (like
-.BR mknod (2)).
+.BR mknod ()).
 
 If
 .I pathname

man2/mmap.2

@@ -271,7 +271,7 @@ Therefore major faults might happen later on.
 So the semantic is not as strong as
 .BR mlock (2).
 One should use
-.BR mmap (2)
+.BR mmap ()
 plus
 .BR mlock (2)
 when major faults are not acceptable after the initialization of the mapping.

man2/modify_ldt.2

@@ -184,12 +184,12 @@ instead, except on extremely old kernels that do not support those system
 calls.
 .PP
 The normal use for
-.BR modify_ldt (2)
+.BR modify_ldt ()
 is to run legacy 16-bit or segmented 32-bit code.
 Not all kernels allow 16-bit segments to be installed, however.
 .PP
 Even on 64-bit kernels,
-.BR modify_ldt (2)
+.BR modify_ldt ()
 cannot be used to create a long mode (i.e., 64-bit) code segment.
 The undocumented field "lm" in
 .IR user_desc

man2/mount.2

@@ -469,7 +469,7 @@ Make this mount unbindable.
 This is like a private mount,
 and in addition this mount can't be bind mounted.
 When a recursive bind mount
-.RB ( mount (2)
+.RB ( mount ()
 with the
 .BR MS_BIND
 and

man2/open.2

@@ -1180,7 +1180,7 @@ inherits duplicates of its parent's file descriptors,
 and those duplicates refer to the same open file descriptions.
 
 Each
-.BR open (2)
+.BR open ()
 of a file creates a new open file description;
 thus, there may be multiple open file descriptions
 corresponding to a file inode.

man2/prctl.2

@@ -94,7 +94,7 @@ is removed from the ambient set.
 .TP
 .B PR_CAP_AMBIENT_IS_SET
 The
-.BR prctl (2)
+.BR prctl ()
 call returns 1 if the capability in
 .I arg3
 is in the ambient set and 0 if it is not.

man2/ptrace.2

@@ -2080,7 +2080,7 @@ is highly specific to the operating system and architecture.
 .\"
 .SS Ptrace access mode checking
 Various parts of the kernel-user-space API (not just
-.BR ptrace (2)
+.BR ptrace ()
 operations), require so-called "ptrace access mode" checks,
 whose outcome determines whether an operation is permitted
 (or, in a few cases, causes a "read" operation to return sanitized data).
@@ -2311,7 +2311,7 @@ the
 file (available since Linux 3.4)
 .\" commit 2d514487faf188938a4ee4fb3464eeecfbdcf8eb
 can be used to restrict the ability to trace a process with
-.BR ptrace (2)
+.BR ptrace ()
 (and thus also the ability to use tools such as
 .BR strace (1)
 and

man2/restart_syscall.2

@@ -115,7 +115,7 @@ In the case of system calls that take a timeout argument and
 automatically restart after a stop signal plus
 .BR SIGCONT ,
 but which do not have the
-.BR restart_syscall (2)
+.BR restart_syscall ()
 mechanism built in, then, after the process resumes execution,
 the time that the process spent in the stop state is
 .I not

man2/seccomp.2

@@ -168,7 +168,7 @@ dangerous things because it did not actually drop privileges.)
 If
 .BR prctl (2)
 or
-.BR seccomp (2)
+.BR seccomp ()
 is allowed by the attached filter, further filters may be added.
 This will increase evaluation time, but allows for further reduction of
 the attack surface during execution of a thread.

man2/semop.2

@@ -472,7 +472,7 @@ On Linux, this limit can be read and modified via the third field of
 this limit should not be raised above 1000,
 .\" See comment in Linux 3.19 source file include/uapi/linux/sem.h
 because of the risk of that
-.BR semop (2)
+.BR semop ()
 fails due to kernel memory fragmentation when allocating memory to copy the
 .IR sops
 array.

man2/set_thread_area.2

@@ -104,9 +104,9 @@ set appropriately.
 \fIu_info\->entry_number\fP is out of bounds.
 .TP
 .B ENOSYS
-.BR get_thread_area (2)
+.BR get_thread_area ()
 or
-.BR set_thread_area (2)
+.BR set_thread_area ()
 was invoked as a 64-bit system call.
 .TP
 .B ESRCH
@@ -129,7 +129,7 @@ In the unlikely event that you want to call them directly, use
 .PP
 .BR arch_prctl (2)
 can interfere with
-.BR set_thread_area (2).
+.BR set_thread_area ().
 See
 .BR arch_prctl (2)
 for more details.

man2/symlink.2

@@ -251,7 +251,7 @@ If this behavior is not desired, use
 On older kernels where
 .BR symlinkat ()
 is unavailable, the glibc wrapper function falls back to the use of
-.BR symlink (2).
+.BR symlink ().
 When
 .I linkpath
 is a relative pathname,

man2/umount.2

@@ -166,11 +166,11 @@ programs intended to be portable.
 .SH NOTES
 .SS umount() and shared mount points
 Shared mount points cause any mount activity on a mount point, including
-.BR umount (2)
+.BR umount ()
 operations, to be forwarded to every shared mount point in the
 peer group and every slave mount of that peer group.
 This means that
-.BR umount (2)
+.BR umount ()
 of any peer in a set of shared mounts will cause all of its
 peers to be unmounted and all of their slaves to be unmounted as well.
 
@@ -183,10 +183,10 @@ onto a subdirectory and then later unmounting that subdirectory with
 will cause every mount in the mount namespace to be lazily unmounted.
 
 To ensure
-.BR umount (2)
+.BR umount ()
 does not propagate in this fashion,
 the mount point may be remounted using a
-.BR mount (2)
+.BR mount ()
 call with a
 .I mount_flags
 argument that includes both
@@ -194,7 +194,7 @@ argument that includes both
 and
 .BR MS_PRIVATE
 prior to
-.BR umount (2)
+.BR umount ()
 being called.
 .SS Historical details
 The original

man2/unlink.2

@@ -283,7 +283,7 @@ POSIX.1-2008.
 On older kernels where
 .BR unlinkat ()
 is unavailable, the glibc wrapper function falls back to the use of
-.BR unlink (2)
+.BR unlink ()
 or
 .BR rmdir (2).
 When

man3/error.3

@@ -152,7 +152,7 @@ one of the two variables is modified.
 After that,
 .BR error_at_line (3)
 is very much like
-.BR error (3).
+.BR error ().
 .SH CONFORMING TO
 These functions and variables are GNU extensions, and should not be
 used in programs intended to be portable.

man3/getnetent.3

@@ -187,10 +187,10 @@ In the above table,
 in
 .I race:netent
 signifies that if any of the functions
-.BR setnetent (3),
-.BR getnetent (3),
+.BR setnetent (),
+.BR getnetent (),
 or
-.BR endnetent (3)
+.BR endnetent ()
 are used in parallel in different threads of a program,
 then data races could occur.
 .SH CONFORMING TO

man3/getprotoent.3

@@ -182,10 +182,10 @@ In the above table,
 in
 .I race:protoent
 signifies that if any of the functions
-.BR setprotoent (3),
-.BR getprotoent (3),
+.BR setprotoent (),
+.BR getprotoent (),
 or
-.BR endprotoent (3)
+.BR endprotoent ()
 are used in parallel in different threads of a program,
 then data races could occur.
 .SH CONFORMING TO

man3/getservent.3

@@ -199,10 +199,10 @@ In the above table,
 in
 .I race:servent
 signifies that if any of the functions
-.BR setservent (3),
-.BR getservent (3),
+.BR setservent (),
+.BR getservent (),
 or
-.BR endservent (3)
+.BR endservent ()
 are used in parallel in different threads of a program,
 then data races could occur.
 .SH CONFORMING TO

man3/getutent.3

@@ -200,14 +200,14 @@ In the above table,
 in
 .I race:utent
 signifies that if any of the functions
-.BR setutent (3),
-.BR getutent (3),
-.BR getutid (3),
-.BR getutline (3),
-.BR pututline (3),
-.BR utmpname (3),
+.BR setutent (),
+.BR getutent (),
+.BR getutid (),
+.BR getutline (),
+.BR pututline (),
+.BR utmpname (),
 or
-.BR endutent (3)
+.BR endutent ()
 are used in parallel in different threads of a program,
 then data races could occur.
 .SH CONFORMING TO

man3/glob.3

@@ -304,7 +304,7 @@ or
 .BR endutent (3)
 are used in parallel in different threads of a program,
 then data races could occur.
-.BR glob (3)
+.BR glob ()
 calls those functions,
 so we use race:utent to remind users.
 .SH CONFORMING TO

man3/login.3

@@ -139,9 +139,9 @@ or
 .BR endutent (3)
 are used in parallel in different threads of a program,
 then data races could occur.
-.BR login (3)
+.BR login ()
 and
-.BR logout (3)
+.BR logout ()
 calls those functions,
 so we use race:utent to remind users.
 .SH CONFORMING TO

man3/setjmp.3

@@ -200,7 +200,7 @@ argument.
 
 .BR setjmp ()
 and
-.BR longjmp (3)
+.BR longjmp ()
 can be useful for dealing with errors inside deeply nested function calls
 or to allow a signal handler to pass control to
 a specific point in the program,
@@ -223,11 +223,11 @@ after a call to
 if they meet all the following criteria:
 .IP \(bu 3
 they are local to the function that made the corresponding
-.BR setjmp (3)
+.BR setjmp ()
 call;
 .IP \(bu
 their values are changed between the calls to
-.BR setjmp (3)
+.BR setjmp ()
 and
 .BR longjmp ();
 and

man3/setnetgrent.3

@@ -128,12 +128,12 @@ In the above table,
 in
 .I race:netgrent
 signifies that if any of the functions
-.BR setnetgrent (3),
-.BR getnetgrent_r (3),
-.BR innetgr (3),
-.BR getnetgrent (3),
+.BR setnetgrent (),
+.BR getnetgrent_r (),
+.BR innetgr (),
+.BR getnetgrent (),
 or
-.BR endnetgrent (3)
+.BR endnetgrent ()
 are used in parallel in different threads of a program,
 then data races could occur.
 .SH CONFORMING TO

man3/wordexp.3

@@ -215,7 +215,7 @@ or
 .BR endutent (3)
 are used in parallel in different threads of a program,
 then data races could occur.
-.BR wordexp (3)
+.BR wordexp ()
 calls those functions,
 so we use race:utent to remind users.
 .SH CONFORMING TO

man7/epoll.7

@@ -182,7 +182,7 @@ and an event happens which wakes the device from sleep, the device
 driver will keep the device awake only until that event is queued.
 To keep the device awake until the event has been processed,
 it is necessary to use the
-.BR epoll (7)
+.BR epoll_ctl (2)
 .B EPOLLWAKEUP
 flag.