summaryrefslogtreecommitdiffstats
path: root/man2 (follow)
Commit message (Collapse)AuthorAgeLines
* man/, share/mk/: Move man*/ to man/Alejandro Colomar2024-05-02-99951/+1
| | | | | | | | | | | | | | | | | | | | This is a scripted change: $ mkdir man/; $ mv man* man/; $ ln -st . man/man*; $ find share/mk/ -type f \ | xargs grep -l '^MANDIR *:=' \ | xargs sed -i '/^MANDIR *:=/s,$,/man,'; $ find share/mk/dist/ -type f \ | xargs grep -l man \ | xargs sed -i 's,man%,man/%,g'; Link: <https://lore.kernel.org/linux-man/YxcV4h+Xn7cd6+q2@pevik/T/> Cc: Petr Vorel <pvorel@suse.cz> Cc: Jakub Wilk <jwilk@jwilk.net> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* mount_setattr.2: Update supported file-systemsRodrigo Campos2024-04-29-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's update the list with the latest file-systems that added support. You can easily verify this by "git grep FS_ALLOW_IDMAP" on the given Linux version to see that the fs is listed and then checkout the previous Linux version to see that it is not listed, therefore it was added in that version. $ diff -w -U0 \ <(git grep FS_ALLOW_IDMAP v6.8 | sed 's/^v6.8://') \ <(git grep FS_ALLOW_IDMAP v6.9-rc4 | sed 's/^v6.9-rc4://') \ | tail -n+4; +fs/hugetlbfs/inode.c: .fs_flags = FS_ALLOW_IDMAP, $ diff -w -U0 \ <(git grep FS_ALLOW_IDMAP v6.6 | sed 's/^v6.6://') \ <(git grep FS_ALLOW_IDMAP v6.7 | sed 's/^v6.7://') \ | tail -n+4; +fs/ceph/super.c: .fs_flags = FS_RENAME_DOES_D_MOVE | FS_ALLOW_IDMAP, $ diff -w -U0 \ <(git grep FS_ALLOW_IDMAP v6.2 | sed 's/^v6.2://') \ <(git grep FS_ALLOW_IDMAP v6.3 | sed 's/^v6.3://') \ | tail -n+4; +mm/shmem.c: .fs_flags = FS_USERNS_MOUNT | FS_ALLOW_IDMAP, $ diff -w -U0 \ <(git grep FS_ALLOW_IDMAP v6.1 | sed 's/^v6.1://') \ <(git grep FS_ALLOW_IDMAP v6.2 | sed 's/^v6.2://') \ | tail -n+4; +fs/squashfs/super.c: .fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP, Signed-off-by: Rodrigo Campos <rodrigo@sdfg.com.ar> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man2/: Add MPOL_WEIGHTED_INTERLEAVE documentationSvetly Todorov2024-04-26-3/+43
| | | | | | | | | | | | | | | | | Add documentation for the new MPOL_WEIGHTED_INTERLEAVE mode in the same manual pages that mention MPOL_INTERLEAVE; namely, mbind(2), set_mempolicy(2), and get_mempolicy(2). Descriptions were based on the changes introduced in this patch: <https://lore.kernel.org/all/20240202170238.90004-4-gregory.price@memverge.com/> Which was upstreamed to 6.9 here: <https://lore.kernel.org/linux-mm/20240313200532.34e4cff216acd3db8def4637@linux-foundation.org/> Cc: gregory.price@memverge.com Reviewed-by: "Huang, Ying" <ying.huang@intel.com> Signed-off-by: Svetly Todorov <svetly.todorov@memverge.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* open.2: protected_* sysctls are defined in proc_sys_fs(5), not proc(5)Emanuele Torre2024-04-26-1/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* syscalls.2: srcfixG. Branden Robinson2024-04-17-3/+4
| | | | | | | | Tweak input format of table text blocks to make a planned sed-driven update simpler and more reliable. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* getpagesize.2: tfixG. Branden Robinson2024-04-17-1/+1
| | | | | Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* init_module.2: Document MODULE_INIT_COMPRESS_FILE flagMichael Weiß2024-04-04-0/+51
| | | | | | | | | | | | | | | | | | | | | | | | finit_module() supports the MODULE_INIT_COMPRESS_FILE flag since Linux 5.17. See commit b1ae6dc41eaaa ("module: add in-kernel support for decompressing") During implementation of a secure module loader in GyroidOS, we wanted to filter unsafe module parameters. To verify that only the two documented flags which are disabling sanity checks are unsafe, we had a look in the current kernel implementation. We discovered that this new flag MODULE_INIT_COMPRESS_FILE was added. Having a deeper look at the code, we also discovered that a new error code EOPNOTSUPP is possible within newer kernels. The inital commit only supported gzip and xz compression algorithms. Support for zstd was added in Linux 6.2 by commit 169a58ad824d8 ("module/decompress: Support zstd in-kernel decompression") Signed-off-by: Michael Weiß <michael.weiss@aisec.fraunhofer.de> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* getpagesize.2, syscalls.2: ModernizationElliott Hughes2024-03-31-40/+20
| | | | | | | | | | | | | | | | | | | | Remove the HP-UX portability advice, since getpagesize() is a slightly better option than sysconf() for Linux systems. Explain why this function exists, and why this man page is in the wrong section. (The previous text tried to do both at the same, which was confusing.) Also explain how the vast majority of architectures that don't have a syscall (but do support multiple page sizes) actually work. Also de-emphasize the glibc 2.0 bug, since most people don't need to worry about compatibility with versions of glibc from 1997. Finally, change "not on x86" in syscalls.2 to say where there _is_ a syscall. Co-developed-by: Elliott Hughes <enh@google.com> Co-developed-by: Alejandro Colomar <alx@kernel.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* shmop.2: EXAMPLES: ffixAlejandro Colomar2024-03-26-3/+3
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: EXAMPLES: Add include guardsAlejandro Colomar2024-03-26-0/+5
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: EXAMPLES: Fix includesAlejandro Colomar2024-03-26-5/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* bpf.2: wfixJing Peng2024-03-18-1/+1
| | | | | Signed-off-by: Jing Peng <pj.hades@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* getrusage.2, proc_pid_io.5: Crosslinkнаб2024-03-14-1/+2
| | | | | | | These serve the same purpose from different perspectives. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* getrusage.2: proc(5) /proc/pid/stat -> proc_pid_stat(5)наб2024-03-14-6/+2
| | | | | | Fixes: bbc21bc4dbef ("proc.5, proc_pid_stat.5: Split /proc/PID/stat from proc(5)") Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* read.2: tfixHugo Gabriel Eyherabide2024-03-12-1/+1
| | | | | Signed-off-by: Hugo Gabriel Eyherabide <hugogabiel.eyherabide@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* clock_getres.2: HISTORY: Clarify that POSIX.1-2008 only makes mandatory the ↵Alejandro Colomar2024-03-05-1/+2
| | | | | | | | | | | functions The different clocks are still optional. Closes: <https://bugzilla.kernel.org/show_bug.cgi?id=218452> Fixes: 4131356cdab8 ("man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY: Reorganize sections") Reported-by: Enrique Garcia <cquike@arcor.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* clock_nanosleep.2: Use 't' rather than 'request'Alejandro Colomar2024-03-05-8/+8
| | | | | | | | | It seems much more clear. Cc: Elliott Hughes <enh@google.com> Cc: Stefan Puiu <stefan.puiu@gmail.com> Cc: Bruno Haible <bruno@clisp.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* nanosleep.2: Use 'duration' rather than 'request'Alejandro Colomar2024-03-03-7/+8
| | | | | | | | | It seems much more clear. Suggested-by: Elliott Hughes <enh@google.com> Cc: Stefan Puiu <stefan.puiu@gmail.com> Cc: Bruno Haible <bruno@clisp.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: epoll_*(), fcntl(), flock(), ioctl(), msgctl(), *prctl(), ptrace(), ↵Alejandro Colomar2024-03-03-204/+211
| | | | | | | | | quotactl(), reboot(), semctl(), shmctl(), lockf(): Consistently use 'op' and 'operation' Reported-by: Bruno Haible <bruno@clisp.org> Cc: Elliott Hughes <enh@google.com> Cc: Stefan Puiu <stefan.puiu@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* process_madvise.2: Fix comments about commit idsAlejandro Colomar2024-02-28-1/+2
| | | | | | | | | | | | | Move the comment about the Linux commit id, specify that it's a Linux commit, and add the glibc commit id too. Link: <https://sourceware.org/bugzilla/show_bug.cgi?id=27380> Link: <https://lore.kernel.org/linux-man/Zd5fMGvIlmhQyONs@thunder.hadrons.org/T/#m9129640e1293a94ff1606a2f973522f40c968306> Fixes: 28628d826661 ("process_madvise.2: Document the glibc wrapper") Reported-by: Guillem Jover <guillem@hadrons.org> Cc: Florian Weimer <fweimer@redhat.com> Cc: Carlos O'Donell <carlos@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* share/mk/, man*/: build-ex: Skip expected failuresAlejandro Colomar2024-02-26-2/+2
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: srcfixAlejandro Colomar2024-02-25-18/+18
| | | | | | | | | | | | | | | | | | | | | | | | | Found with: $ grep -rn '"""' man* \ | grep -v '"""""""""""' \ | sed 's/:.*//' \ | sort \ | uniq; man2/add_key.2 man2/getrlimit.2 man2/keyctl.2 man2/pivot_root.2 man2/request_key.2 man3/isalpha.3 man3/setlocale.3 man3/toupper.3 man7/capabilities.7 man7/cgroups.7 man7/keyrings.7 man7/locale.7 man7/user_namespaces.7 Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: ffixAlejandro Colomar2024-02-25-3/+3
| | | | | | | | | | | | | | | | Found with: $ grep -rn '^\.[BI] .* [.,:;)]*$' man* man2/prctl.2:382:.B FR=1 . man2/openat2.2:377:.B EAGAIN . man2/openat2.2:424:.I how.resolve . man5/elf.5:788:.B PF_R . man5/networks.5:18:.I name number aliases ... man5/protocols.5:31:.I protocol number aliases ... man7/cgroups.7:980:.I """max""" . Cc: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* process_madvise.2: Rename parameter, and use array syntaxAlejandro Colomar2024-02-25-7/+7
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* process_madvise.2: Document the glibc wrapperAlejandro Colomar2024-02-25-15/+5
| | | | | | | | | | | | | $ grepc -n process_madvise /usr/include/ /usr/include/x86_64-linux-gnu/bits/mman_ext.h:25: extern __ssize_t process_madvise (int __pid_fd, const struct iovec *__iov, size_t __count, int __advice, unsigned __flags) __THROW; Reported-by: Florian Weimer <fweimer@redhat.com> Cc: Carlos O'Donell <carlos@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* sigaction.2: HISTORY: Some constants are or were XSI extensionsAlejandro Colomar2024-02-25-1/+9
| | | | | | | Link: <https://lore.kernel.org/linux-man/20240214095707.1824c25c@plasteblaster/T/> Reported-by: Thomas Orgis <thomas@orgis.org> Cc: Eric Blake <eblake@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* sigaction.2: HISTORY: SA_NOCLDSTOP wasn't added in POSIX.1-2001Alejandro Colomar2024-02-25-1/+0
| | | | | | | | | It already existed in POSIX.1-1996, according to just a few lines above. Link: <https://lore.kernel.org/linux-man/20240214095707.1824c25c@plasteblaster/T/> Cc: Thomas Orgis <thomas@orgis.org> Cc: Eric Blake <eblake@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* getdents.2: Add note to misleading field "d_off" in struct linux_dirent64Vinícius Schütz Piva2024-02-25-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The getdents.2 man page details a pair syscalls: getdents() and getdents64(), both of which are used to get the entries of a directory. The results are populated into a structure, with the difference between both syscalls being mostly bitwidth related. However, the behaviour or the 'd_off' field in both struct linux_dirent and linux_dirent64 is wrongly documented in this man page. According to the current manual page, 'd_off' is used to store the "Offset to the next linux_dirent [...] the distance from the start of the directory to the start of the next linux_dirent." This value, though, is filesystem dependent, and much of the time it stores no such offset. According to readdir.3 [1] manpage: > The value returned in d_off is the same as would be returned by > calling telldir(3) at the current position in the directory stream. > Be aware that despite its type and name, the d_off field is seldom > any kind of directory offset on modern filesystems. Applications > should treat this field as an opaque value, making no assumptions > about its contents; see also telldir(3). Of course, readdir(3) is a glibc function with no ties to getdents(2), but it was implemented with such syscall and considering that readdir(3) doesn't process the data from getdents(2) my belief is that it inherited said behaviour from it [2]. telldir(3) tells a similar story. On the example provided at the end of getdents.2, notable is the d_off value of the very last entry: --------------- nread=120 --------------- inode# file type d_reclen d_off d_name 2 directory 16 12 . 2 directory 16 24 .. 11 directory 24 44 lost+found 12 regular 16 56 a 228929 directory 16 68 sub 16353 directory 16 80 sub2 130817 directory 16 4096 sub3 which makes a very sudden jump that is obviously not where the entry is located. Rerunning this same example but on a ext4 partition gives you garbage values: --------------- nread=176 --------------- inode# file type d_reclen d_off d_name 2050 directory 24 4842312636391754590 sub2 2 directory 24 4844777444668968292 .. 2051 directory 24 7251781863886579875 sub3 12 regular 24 7470722685224223838 a 2049 directory 24 7653193867028490235 sub 11 directory 32 7925945214358802294 lost+found 2 directory 24 9223372036854775807 . In fact, I've had a hard time reproducing nice d_off values on ext2 too, so what the filesystem does with d_off must have change since then. On tmpfs it's a count: --------------- nread=144 --------------- inode# file type d_reclen d_off d_name 1 directory 24 1 . 1 directory 24 2 .. 5 directory 24 3 sub3 4 directory 24 4 sub2 3 directory 24 5 sub 2 regular 24 6 a I've also not been the first to notice this, as you can see from this stackoverflow issue opened last year: https://stackoverflow.com/q/75119224 Safe to say, it's a very unreliable field. Below is a patch that adds a warning besides the d_off field in both structures, plus a brief explanation on why this field can be mislea- ding (while also directing the user towards the readdir.3 man page). Link: [1] <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man3/readdir.3> Link: [2] <https://elixir.bootlin.com/glibc/glibc-2.39/source/sysdeps/unix/sysv/linux/readdir.c> Signed-off-by: Vinícius Schütz Piva <vinicius.vsczpv@outlook.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* close_range.2: srcfixAlejandro Colomar2024-02-25-1/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* close_range.2: Add _GNU_SOURCE and <unistd.h> to SYNOPSISMark Wielaard2024-02-18-5/+8
| | | | | | | | | | | | | | | close_range() is defined in <unistd.h> when _GNU_SOURCE is defined. The <linux/close_range.h> header file only defines the (linux-specific) flags constants. The flags argument is an int, not an unsigned int, in the glibc wrapper. Use the close_range() library call in the example code instead of syscall(). Fixes: 71a62d6c3c56 ("close_range.2: Glibc added a wrapper recently") Fixes: c2356ba085ed ("close_range.2: Glibc 2.34 has added a close_range() wrapper") Reported-by: Alexandra Hájková <ahajkova@redhat.com> Signed-off-by: Mark Wielaard <mark@klomp.org> [alx: ffix] Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: tfixŠtěpán Němec2024-02-18-6/+6
| | | | | Signed-off-by: Štěpán Němec <stepnem@smrk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: ffixAlejandro Colomar2024-02-12-1/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* seteuid.2: glibc implements seteuid() calling setresuid(), not setreuid()Štěpán Němec2024-02-11-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Analogously with set*gid(). This has been the case since more than two decades, e.g.: commit eae59a5681a6 glibc-2.3.2-793-geae59a5681a6 Commit: Ulrich Drepper <drepper@redhat.com> CommitDate: Sun Jun 8 22:37:53 2003 +0000 Update. * sysdeps/unix/sysv/linux/seteuid.c (seteuid): Use setresuid32 syscall directly if possible. If __ASSUME_SETRESUID_SYSCALL is defined drop compatibility code. [...] The change in implementation from setreuid()/setregid() is also already mentioned two paragraphs earlier in the same man page. Fixes: a36b2bb0eca4 ("seteuid.2: seteuid() and setegid() are implemented as library functions") Fixes: 8554dd0324b0 ("seteuid.2: tfix") Signed-off-by: Štěpán Němec <stepnem@smrk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: Say ISO/IEC 8208Alejandro Colomar2024-01-28-1/+1
| | | | | | | Link: <https://www.iso.org/standard/33080.html> Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: Use '(date)' in TH lineAlejandro Colomar2024-01-28-1/+1
| | | | | | It seems those dates were accidentally hardcoded. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* open.2: srcfixG. Branden Robinson2024-01-16-1/+3
| | | | | | | | Migrate man page cross reference in non-filled context to font alternation macro. This is to prepare it for `MR` migration. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* syscalls.2: ffixG. Branden Robinson2024-01-16-5/+5
| | | | | | | | | | | | Refactor table format specification: use column modifiers to set heading rows in bold instead of populating every entry in them with font selection escape sequences. Use a single '_' to indicate a horizontal rule spanning the table. Put vertical space before the table (making it resemble a typographical "display") rather than after the after the column heading. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* mremap.2: wfixG. Branden Robinson2024-01-16-4/+9
| | | | | | | | | | Recast to use language paralleling that of the MREMAP_DONTUNMAP discussion elsewhere in the page. Spotted these (excessively?) abbreviated cross references while preparing for the `MR` man(7) macro migration. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* faccessat(2), utimensat(2): Document AT_EMPTY_PATH flagRenzo Davoli2024-01-01-2/+44
| | | | | | | | | | | | | utimensat() and faccessat() support the flag AT_EMPTY_PATH since Linux 5.8. (actually Linux 5.8 added faccessat2(): glibc wrapper for faccessat() uses faccessat2(), and faccessat2() does support AT_EMPTY_PATH). Reuse the standard text used in many other -at manual pages. Signed-off-by: Renzo Davoli <renzo@cs.unibo.it> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* swapon.2: MAX_SWAPFILES: Clarify limit after decreaseYang Xu2023-12-22-2/+2
| | | | | Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* ioctl_console.2: Document new CAP_SYS_ADMIN restrictions (since Linux 6.7)Günther Noack2023-12-21-0/+12
| | | | | | | | | | | Since Linux commit 8d1b43f6a6df7bce ("tty: Restrict access to TIOCLINUX' copy-and-paste subcommands"), the TIOCL_SETSEL, TIOCL_PASTESEL and TIOCL_SELLOADLUT subcommands require CAP_SYS_ADMIN. Cc: Hanno Böck <hanno@hboeck.de> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Günther Noack <gnoack@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* sendfile.2: Pull in_fd type requirements up to 6.7наб2023-12-21-1/+10
| | | | | | | | | | | | | | But this does mean that since 5.12, it supports (5.12 has ISREG|ISBLK, this actually matches 6.0 semantics): any -> pipe via splice seekable -> any Also, there are many seekable files which aren't regular, and the offset is updated regardless. This is obvious, but the wording is clumsy. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* swapon.2: Adjust decreased value under CONFIG_PTE_MARKERYang Xu2023-12-17-0/+4
| | | | | | | | | Since linux 5.19[1], MAX_SWAPFILES will be futher decreased 1 if kernel built with CONFIG_PTE_MARKER. Link: [1] <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/linux/swap.h?id=679d10331> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* swapon.2: Adjust decreased value under CONFIG_MIGRATIONYang Xu2023-12-17-1/+2
| | | | | | | | Since Linux 5.19[1], the limit is decreased by 3 instead of 2. Link: [1] <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/linux/swap.h?id=6c287605f> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* mbind.2: Add mode flag MPOL_F_NUMA_BALANCINGYafang Shao2023-12-09-0/+17
| | | | | | | | | | | | | | | | | | | | | In Linux Kernel 5.12, a new mode flag, MPOL_F_NUMA_BALANCING, was added to set_mempolicy() to optimize the page placement among the NUMA nodes with the NUMA balancing mechanism even if the memory of the applications is bound with MPOL_BIND. In Linux Kernel 5.15, this mode flag was extended to mbind(2). Let's also add man-page for mbind(2). It is copied from set_mempoicy(2) man-page with subtle modifications. Related kernel commits: bda420b985054a3badafef23807c4b4fa38a3dff 6d2aec9e123bb9c49cb5c7fc654f25f81e688e8c Suggested-by: "Huang, Ying" <ying.huang@intel.com> Signed-off-by: Yafang Shao <laoar.shao@gmail.com> Cc: "Huang, Ying" <ying.huang@intel.com> Cc: Michael Kerrisk <mtk.manpages@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: srcfixG. Branden Robinson2023-11-19-4/+14
| | | | | | | | | | | | | | | | | Clean up in preparation for "MR sed". Format only one man page cross reference per input line. Begin parentheticals on their own input lines. Also, groff 1.23.0's (and Plan 9 from User Space's) `MR` is not a font style alternation macro; there is no "reversed" form as with `BR` and `RB`. So when a man page cross reference must be immediately preceded by punctuation, put that punctuation on the previous text line and use the `\c` escape sequence to connect them. Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: Improve timestamp documentationPaul Eggert2023-11-11-33/+45
| | | | | | | Improve discussion of leap seconds, year-2038 etc. Cc: Elliott Hughes <enh@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* readlink.2: tfix (Remove repeated word)Alejandro Colomar2023-11-01-1/+1
| | | | | | | Fixes: f06a3f30fa66 ("readlink.2: Fix an off-by-one error in example code") Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* syscalls.2: wfixAlejandro Colomar2023-11-01-3/+3
| | | | | | | Fixes: b324e17d3208 ("Many pages: wfix") Reported-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* syscalls.2: Mention Linux 6.x seriesAlejandro Colomar2023-11-01-1/+2
| | | | | | Suggested-by: Helge Kreutzmann <debian@helgefjell.de> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-01 12:55:01 +0000