man/man2/truncate.2: ERRORS: Add ENOSPC

This error can be observed for example on a vfat file system that
does not support extending a file without allocating the space.

Signed-off-by: Zeno Sebastian Endemann <zeno.endemann@mailbox.org>
Message-ID: <20260412144007.27323-1-zeno.endemann@mailbox.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man?/io_*.?: Separate documentation of system calls and of libaio wrappers

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_submit.2: Refer to io_submit(3) from libaio

And reduce our documentation of the wrapper.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_submit.2: SYNOPSIS: Use array notation

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_submit.2: Reduce parameter name

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_submit.2: SYNOPSIS: Use syscall(2)

We're documenting the raw system call; not the wrapper.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_submit.2: ERRORS: Split EINVAL

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_cancel.2: Refer to io_cancel(3) from libaio

And reduce our documentation of the wrapper.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_getevents.2: Refer to io_getevents(3) from libaio

And reduce our documentation of the wrapper.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_getevents.2: ERRORS: Split EINVAL

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_getevents.2: BUGS: Remove section

A segmentation fault instead of EINVAL is actually possible for many
system calls, not just this one.  That's expected, because it's
undefined behavior in C, and a crash is a usual consequence of an
invalid pointer.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man?/io_destroy.?: Split io_destroy(3) from io_destroy.2

This simplifies the documentation of the system call.
Let the wrapper be documented as io_destroy(3).

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_destroy.2: ERRORS: wfix EFAULT

The text was too similar with the text for EINVAL.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man?/io_setup.?: Split io_setup(3) from io_setup.2

This simplifies the documentation of the system call.
Let the wrapper be documented as io_setup(3).

Cc: Guillem Jover <guillem@debian.org>
Cc: <linux-aio@kvack.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_setup.2: Use syscall(2) in the SYNOPSIS

That's what we do when there's no glibc wrapper.

Also, remove the comment on the existing include, as we usually don't
comment when includes are needed for types; we only comment for
constants.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_setup.2: ERRORS: It is *ctx_idp that must be initialized

Also, clarify that it must be initialized to 0.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_setup.2: ERRORS: Split EINVAL

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_setup.2: Update reference (proc(5) => proc_sys_fs(5))

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/io_setup.2: Reduce parameter name

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/landlock_restrict_self.2, man/man7/landlock.7: Document audit logging (ABI v7)

* Document the flags LANDLOCK_RESTRICT_SELF_LOG_SUBDOMAINS_OFF,
  LANDLOCK_RESTRICT_SELF_LOG_SAME_EXEC_OFF and
  LANDLOCK_RESTRICT_SELF_LOG_NEW_EXEC_ON.
* List these flags in the compatibility table in landlock.7

The documentation text is copied from the kernel documentation,
originally authored by Mickaël Salaün in [1] and [2].

Link[1]: <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux/landlock.h?id=ead9079f75696a028aea8860787770c80eddb8f9>
Link[2]: <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux/landlock.h?id=12bfcda73ac2cf3083c9d6d05724af92da3a4b4b>
Cc: Mickaël Salaün <mic@digikod.net>
Signed-off-by: Günther Noack <gnoack3000@gmail.com>
Message-ID: <20260329124815.92502-5-gnoack3000@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/getdents.2: ffix

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/getdents.2: Document system call interface of getdents64

The count argument of the getdents64 system call is assumed to not exceed
INT_MAX. The glibc function accepts a size_t and passes INT_MAX to the kernel
if count exceeds INT_MAX.

Also document the dirent64 structure in glibc.

Signed-off-by: vursc <vursc@vursc.org>
Message-ID: <20260406092113.184487-2-vursc@vursc.org>
Cc: Mark Harris <mark.hsj@gmail.com>
[alx: ffix]
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man7/hostname.7: A hostname may not end with a hyphen either

On 2026-04-06T19:19:36+0000, Neitzert, Greg A wrote:
> At the bottom of your man page you do refer in the SEE ALSO to the
> pertinent RFCs:
>
>      IETF RFC 1123 ⟨http://www.ietf.org/rfc/rfc1123.txt⟩
>      IETF RFC 1178 ⟨http://www.ietf.org/rfc/rfc1178.txt⟩
>
> RFC 1178 has some general best practices and is not really governing
> for this.  RFC 1123 however, and the RFC it refers back to, RFC-952,
> are directly on point.
>
> RFC UPDATES RFC-952 and refers to it:
>
> "The syntax of a legal Internet host name was specified in RFC-952
>       [DNS:4].  One aspect of host name syntax is hereby changed: the
>       restriction on the first character is relaxed to allow either a
>       letter or a digit.  Host software MUST support this more liberal
>       syntax.
>
>  Host software MUST handle host names of up to 63 characters and
>       SHOULD handle host names of up to 255 characters."
>
>
> Referring back to RFC-952:
>
> "1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
>    to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
>    sign (-), and period (.).  Note that periods are only allowed when
>    they serve to delimit components of "domain style names". (See
>    RFC-921, "Domain Name System Implementation Schedule", for
>    background).  No blank or space characters are permitted as part of
>    a name.  No distinction is made between upper and lower case.  The
>    first character must be an alpha character.  The last character
>    must not be a minus sign or period."
>
>
> Taking RFC 952, and the updates in RFC-1123 we end up with the
> following:
> 1.  Length is now of 63 characters minimum (superceding 24).
> 2.  The first character must be an alpha (or numeric - as amended by
>     RFC 1123).
> 3.  The last character MUST NOT be a minus sign (from RFC 952 and left
>     unchanged).
>
> Therefore, to be accurate with the standard you are referring to
> (RFC 1123 and the RFC it updates 952), I believe you should have:
>
> "A hostname may not start or end with a hyphen."
>
> All of your text is in harmony with RFC 952 and RFC 1123 except for
> the issue regarding the hyphens - at least from my reading.

Reported-by: "Neitzert, Greg A" <greg.neitzert@unisys.com>
Suggested-by: "Neitzert, Greg A" <greg.neitzert@unisys.com>
Message-ID: <DM8PR07MB8854A4169C2DD8BC4DAD6ED0885DA@DM8PR07MB8854.namprd07.prod.outlook.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/landlock_create_ruleset.2: Document scoped field in struct landlock_ruleset_attr (ABI v6)

Add the missing scoped field to the struct landlock_ruleset_attr
definition, and document it as a bitmask of scope flags.

Available since Linux 6.12 (Landlock ABI version 6).

Cc: Tahera Fahimi <fahimitahera@gmail.com>
Cc: Mickaël Salaün <mic@digikod.net>
Fixes: 5a89b5bd (2025-03-06; "man/man7/landlock.7: Document IPC scoping (Landlock ABI v6)")
Signed-off-by: Günther Noack <gnoack3000@gmail.com>
Message-ID: <20260329124815.92502-4-gnoack3000@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/landlock*.2: ERRORS: Reorder alphabetically

Reorder lists of error codes alphabetically, in line with man-pages(7).

Cc: Mickaël Salaün <mic@digikod.net>
Signed-off-by: Günther Noack <gnoack3000@gmail.com>
Message-ID: <20260329124815.92502-3-gnoack3000@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strptime.3: tfix

A little patch to fix a few little issues I noticed in the doc.  I've
never contributed here before so I'm not sure if I'm doing it all
right, if not, apologies!

Message-ID: <CAEMnaZ+paJ5_Dc5FkibQSggqiR9hW7EYLtnn=wmbCz3Cb+iLVw@mail.gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/pthread_cond_init.3: Fix name of mutex unlock function

Fixes: 31b1e42d (2023-10-03; "LinuxThreads library.")
Signed-off-by: Christoph Erhardt <fedora@sicherha.de>
Message-ID: <7245006.9J7NaK4W3v@framework>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Fix incorrect naming of STATMOUNT_MNT_{UID,GID}MAP flags

STATMOUNT_UIDMAP is actually STATMOUNT_MNT_UIDMAP and STATMOUNT_GIDMAP
is STATMOUNT_MNT_GIDMAP.

Fixes: 9968ead5 (2026-03-05; "man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP}")
Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <4f6135c8b84b8b291a7145a72f216e77f8cf0103.1773904035.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Fix STATMOUNT_MNT_{UID,GID}MAP documentation

In case of idmapped mounts and statmount(), three cases can occur:

1. The mount is not an idmapped mount. In this case, smbuf->mask will
   *not* have STATMOUNT_MNT_{UID,GID}MAP set.
2. The mount is an idmapped mount but *all* its mappings are *not*
   resolvable in the user namespace of the caller.
   In this case, smbuf->mask will have STATMOUNT_MNT_{UID,GID}MAP set
   but smbuf->mnt_{uid,gid}map_num will be 0.
3. The mount is an idmapped mount and *all* its mappings are resolvable
   in the user namespace of the caller.
   In this case, smbuf->mask will have STATMOUNT_MNT_{UID,GID}MAP set
   and mbuf->mnt_{uid,gid}map_num will be greater than 0.

The current documentation fails to differentiate between case 1 and 2
and incorrectly states that STATMOUNT_MNT_{UID,GID}MAP will be set for
non-idmapped mounts.

We can verify that the above is the case by looking at [1] and is made
explicitly clear by the comment in the implementation [2]. The case for
STATMOUNT_MNT_{UID,GID}MAP not being raised for a non-idmapped mount can
be verified by running this program [3].

[1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=37c4a9590e1efcae7749682239fc22a330d2d325>
[2]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/namespace.c#n5489>
[3]: <https://gist.github.com/bsach64/674264ec69e592f906b2713c9f95060b>

Fixes: 9968ead5 (2026-03-05; "man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP}")
Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <8e3b0ce5a322e253ddad52e10875ce37c9c005cd.1773904035.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/mmap.2: Document that MAP_GROWSDOWN doesn't affect mmap return value.

The man page states that the MAP_GROWSDOWN flag causes the kernel to
return an address one page lower than the mapping created.  This is not
true; the kernel returns the base address of the mapping created, just
as it does when MAP_GROWSDOWN is not passed.  This can be confirmed by
inspecting "/proc/self/maps" after making a gd mapping, and comparing it
to the returned value from mmap.

You can confirm this by running this example program:

#include <stddef.h>
#include <stdio.h>
#include <stdlib.h>
#include <sys/mman.h>

int
main(void)
{
int   c;
void  *p;
FILE  *f;

p = mmap(NULL, 1 /* rounds up to page */,
         PROT_READ | PROT_WRITE,
         MAP_ANONYMOUS | MAP_PRIVATE | MAP_GROWSDOWN,
         -1, 0);
printf("mmap() return value: %p\n", p);
f = fopen("/proc/self/maps", "r");
while (EOF != (c = fgetc(f)))
putchar(c);

exit(EXIT_SUCCESS);
}

...and observing that the value returned from mmap is the base of a
mapping in "/proc/self/maps".

Fixes: 176b1a76 (2016-11-21; "mmap.2: Add (much) more detail on MAP_GROWSDOWN")
Signed-off-by: Ben Kallus <benjamin.p.kallus.gr@dartmouth.edu>
Message-ID: <20260318144937.2210447-1-benjamin.p.kallus.gr@dartmouth.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man5/proc_pid.5: Clarify which user namespace affects permissions

A more careful reading of fs/proc/base.c (since v4.11, as of v7.0-rc1)
reveals that it is not task->cred->user_ns that is checked, but
task->mm->user_ns, which is set during execve(2) (and copied over in
fork(2) and so on) [1], and is the correct user namespace to check for
ptrace-related purposes.  Clarify the relevant text.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bfedb589252c01fa505ac9f6f2a3d5d68d707ef4

Fixes: ae636827 (2018-07-05; "proc.5: Fix description of /proc/PID/* ownership to account for user namespaces")
Signed-off-by: Vivian Wang <dramforever@live.com>
Message-ID: <OSCPR01MB134682A1A80B8C9FB71CBA64DC640A@OSCPR01MB13468.jpnprd01.prod.outlook.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING.d/patches/trailer: Fixes: Use 8-char hashes

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strcmp.3: Refer to memcmp(3) for several details

It's unnecessary to duplicate the information here.  Let's keep a single
source of truth.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man7/tcp.7: Document effect of TCP_DEFER_ACCEPT on client socket

TCP_DEFER_ACCEPT has an interesting little-known effect on client
sockets.  I don't think it's very useful but should still be documented.

See here for reference:
<https://elixir.bootlin.com/linux/v6.19.6/source/net/ipv4/tcp_input.c#L6781-L6796>

Signed-off-by: Ran Benita <ran@unusedvar.com>
Message-ID: <777621b7-d204-4476-bf98-23a703250db2@app.fastmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man5/core.5: Document the %f and %C core_pattern specifiers

Whilst going through the relevant kernel code in fs/coredump.c,
I noticed that two core pattern specifiers supported by Linux are
missing from man5/core.5.  Document them now.

Signed-off-by: Emanuele Rocca <emanuele.rocca@arm.com>
Message-ID: <abRiap_UrhFzNxPs@NH27D9T0LF>
Acked-by: Oleksandr Natalenko <oleksandr@natalenko.name>
Message-ID: <4718783.LvFx2qVVIh@natalenko.name>
Acked-by: Lepton Wu <ytht.net@gmail.com>
Message-ID: <CALqoU4xVdo_-W+yv7Rf77+G0wG6Dvit5dqZyhmPHpU+Qhbsm=Q@mail.gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/[v]aprintf.3: New page and link page

Link: <https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3750.txt>
Link: <https://gitweb.git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=68143964a370b3a565d081d4d994aee772eaca00>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/clock_getres.2: CLOCK_TAI: Modernize leap-seconds documentation

Give more details about CLOCK_TAI, such as its epoch, its
connection to NTP, and the past and planned future of leap seconds.

Signed-off-by: Paul Eggert <eggert@cs.ucla.edu>
Message-ID: <d3b5a021-9299-466c-b939-c54143034e86@cs.ucla.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/clock_getres.2: Clarify what "TAI" stands for.

Signed-off-by: Paul Eggert <eggert@cs.ucla.edu>
Message-ID: <d3b5a021-9299-466c-b939-c54143034e86@cs.ucla.edu>
[alx: ffix]
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/clock_getres.2: wfix

Tighten up the language.

Signed-off-by: Paul Eggert <eggert@cs.ucla.edu>
Message-ID: <d3b5a021-9299-466c-b939-c54143034e86@cs.ucla.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/clock_getres.2: Some clocks behave differently if the system is suspended

Signed-off-by: Paul Eggert <eggert@cs.ucla.edu>
Message-ID: <d3b5a021-9299-466c-b939-c54143034e86@cs.ucla.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/clock_getres.2: Clarify when clocks are indirectly settable

..., by setting CLOCK_REALTIME.

Signed-off-by: Paul Eggert <eggert@cs.ucla.edu>
Message-ID: <d3b5a021-9299-466c-b939-c54143034e86@cs.ucla.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_BY_FD

STATMOUNT_BY_FD introduces the ability to get information about a mount
using a fd on the mount.  This functionality is currently in linux-next
[1].

Link [1]: <https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20260126&id=d5bc4e31f2a3f301b4214858bec834c67bb2be5c>
Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <57c96336ccfbdc05f60b7875c315a8c1dd0d14b8.1771870334.git.b.sachdev1904@gmail.com>
Message-ID: <7d4b22c595feeadb3be6df8a8781344597120f7e.1771870502.git.b.sachdev1904@gmail.com>
Message-ID: <ef5a337e52f904d7eeb1e3fa82a09b04b46a4860.1772075365.git.b.sachdev1904@gmail.com>
Cc: Askar Safin <safinaskar@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document req.mnt_ns_fd

Document the new mnt_ns_fd parameter to struct mnt_id_req.

req.mnt_ns_fd can be used to query for a mount in a foreign mount
namespace.

The mnt_ns_fd parameter description is based on this commit message [1].

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9020d0d844ad58a051f90b1e5b82ba34123925b9>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <6577568b31ba8700214af1696d740d3b6aa1869d.1771855135.git.b.sachdev1904@gmail.com>
Message-ID: <a250e5c44e03428b5817ee863ebe6b47977ec9ab.1771855680.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK

Document STATMOUNT_SUPPORTED_MASK flag and the corresponding field
introduced by it. It is used to determine the flags supported by the
current kernel. The text is based on this commit message [1].

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f6116b5b77b0536d2ad7482ee42bfe58b8fac01>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <b537e03ab73d8677a53730311b5a3c11ff29a51b.1771855135.git.b.sachdev1904@gmail.com>
Message-ID: <2bf71bae60b181c206326417047ece49f1113940.1771855680.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP}

Document the STATMOUNT_{UIDMAP,GIDMAP} flags and the corresponding
fields introduced by them. Most of this is based on the commit message
provided here [1].

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=37c4a9590e1efcae7749682239fc22a330d2d325>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <6146fa1d59006387ad7996f28f5651787125d956.1771855135.git.b.sachdev1904@gmail.com>
Message-ID: <2c1e23c24b64c5466075dcf5d4ac1595c04b4139.1771855680.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_OPT_SEC_ARRAY

Document STATMOUNT_OPT_SEC_ARRAY flag and the corresponding fields
introduced by it. This text is based this commit message [1].

Retrieves only security options separated by null bytes.

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aefff51e1c2986e16f2780ca8e4c97b784800ab5>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <185c7248b4ee5dbe840904d0b0b3782b29ed6579.1771771560.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_OPT_ARRAY

Document STATMOUNT_OPT_ARRAY flag and the corresponding fields
introduced by it. This text is based on this commit message [1].

Retrieve only file system options, separated by null bytes. For security
opts STATMOUNT_OPT_SEC_ARRAY is used.

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f4d4503e9e5ab765a7948f98bc5deef7850f607>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <4e925a9f871ec408d82db0124300d97200c4a778.1771771560.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_SB_SOURCE

Document STATMOUNT_SB_SOURCE flag and the corresponding field introduced
by it. This text is based on this commit message [1].

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=44010543fc8bedad172aa5b6c43480e5d2124497>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <569933a8b526b89d35e84d5f0af42c7a4711b97f.1771771560.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_FS_SUBTYPE

Document STATMOUNT_FS_SUBTYPE flag and the corresponding field
introduced by it.

STATMOUNT_FS_SUBTYPE retrieves the subtype of a file system, useful for
FUSE mounts (example: fuse.sshfs, where "sshfs" is the subtype).

This work is based on this commit message [1].

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed9d95f691c29748f21bc019de9566b698fdfab7>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <82e6babcdac48155cdb64c6f4b98c058e6f19060.1771771560.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document STATMOUNT_MNT_OPTS

Document STATMOUNT_MNT_OPTS flag and the corresponding field introduced
by it.

STATMOUNT_MNT_OPTS is used to get all mount options on the mount
separated by commas. Similiar to how they are displayed in
/proc/[pid]/mountinfo.

This text is based on this commit [1].

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f9af549d1fd31487bbbc666b5b158cfc940ccc17>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <24ba21cad0766cf8c1666b85684eda154acce16b.1771771560.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: Document req.mnt_ns_id and STATMOUNT_MNT_NS_ID

Document the new mnt_ns_id parameter to struct mnt_id_req and the
STATMOUNT_MNT_NS_ID flag.

req.mnt_ns_id can be used to query for a mount in a foreign mount
namespace.

STATMOUNT_MNT_NS_ID can be used to retreive the mnt_ns_id of the mount
being queried.

The mnt_ns_id parameter description is based on this commit message [1]
and STATMOUNT_MNT_NS_ID text is based on [2].

Link [1]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71aacb4c8c3d19da053363a5fe7538a8af082d56>
Link [2]:
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=09b31295f833031c88419550172703d45c5401e3>

Signed-off-by: Bhavik Sachdev <b.sachdev1904@gmail.com>
Message-ID: <c7cb4bb9b8242009c672ddfd4d6568b8a7dde189.1771771560.git.b.sachdev1904@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/statmount.2: wsfix

This is in preparation for the following commit.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/stpcpy.3: Fix UB in expression

The order of evaluation is undefined, so we must use a length that is
stable.

Reported-by: Bruno Haible <bruno@clisp.org>
Suggested-by: Bruno Haible <bruno@clisp.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING.d/patches/trailer: Don't specify the hash length

We document the exact length in <CONTRIBUTING.d/git>.

Fixes: a8aa0eaf (2026-02-08; "CONTRIBUTING.d/: Document format of 'Fixes:' trailer fields")
Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING.d/git: core.abbrev: Use only 8 characters

8 characters is enough for showing most commits unambiguously.

12 would be necessary if we didn't have the date.  However, the date can
be used to disambiguate a commit better than a longer hash.  Let's cut
some characters to make commit references more readable.

Fixes: a8aa0eaf (2026-02-08; "CONTRIBUTING.d/: Document format of 'Fixes:' trailer fields")
Fixes: e9fa66a0 (2026-02-08; "CONTRIBUTING.d/git: core.abbrev: Set to 12")
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/: Document how string functions relate to each other

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strcpy.3: Compare str{cpy,cat}(3) to stpcpy(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/stpcpy.3: Compare stpcpy(3) to strcpy(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/stpcpy.3: Compare stpcpy(3) to other string functions

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/streq.3: Compare streq(3) to strcmp(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strlen.3: Compare strlen(3) to strnul(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strncat.3: Compare strncat(3) to other string functions

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strcmp.3: Compare str[n]cmp(3) to memcmp(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/stpncpy.3: Compare st[rp]ncpy(3) to other string functions

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strdupa.3: Compare str[n]dupa(3) to other functions

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strnlen.3: Compare strnlen(3) to memchr(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strspn.3: Compare strcspn(3) to strpbrk(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strstr.3: Compare strstr(3) to memmem(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strchr.3: Compate strchr(3) to strpbrk(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strchr.3: Compare str[r]chr(3) to mem[r]chr(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strnul.3: Compare strnul(3) to strlen(3) and strchr(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strchrnul.3: Compare strchrnul(3) to strcspn(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strchrnul.3: Compare strchrnul(3) to strchr(3) and strnul(3)

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strchr.3: Remove obvious paragraph

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strchrnul.3: RETURN VALUE: Remove parenthetical

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/str*.3: ffix, wfix

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/st[rp]cpy.3: Split stpcpy(3) to a separate page

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/str[n]dup[a].3: Split str[n]dupa(3) to a separate page

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strtok{,_r}.3: Split strtok_r(3) to a separate page

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/{raw,}memchr.3: Split rawmemchr(3) to a separate page

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strchr{,nul}.3: Split strchrnul(3) to a separate page

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/str{sep,tok}.3: CAVEATS: Remove obvious statements

These are obvious from the fact that the first argument is non-const.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strtok.3: Rename BUGS => CAVEATS

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/string.3: Move text from SYNOPSIS to DESCRIPTION

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/string.3: Remove index(3) and rindex(3)

They're deprecated; their own manual page is enough.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING.d/style/c: Split subsections

Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING.d/style/c: Add 'Alignment' subsection

Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING.d/style/c: Use tabs for indentation

I'm going to eventually convert everything to tabs.  It's simpler, and
it allows me to paste code directly to the examples.

Signed-off-by: Alejandro Colomar <alx@kernel.org>

etc/shellcheck/shellcheckrc, share/mk/: Move exception to shellcheckrc

Fixes: 78488ed5ccbb (2025-11-06; "share/mk/: $SHELLCHECKFLAGS: Disable SC2028")
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/s390_guarded_storage.2: HISTORY: ffix

Signed-off-by: Seth McDonald <dev@sethm.id.au>
Message-ID: <464d2acd9d6246ae40849738f6b5ff6151ae9e97.1771750388.git.dev@sethm.id.au>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/readv.2: HISTORY: ffix

Signed-off-by: Seth McDonald <dev@sethm.id.au>
Message-ID: <f336517a9084b23f49da379a4d2a73f7a86c2e32.1771750388.git.dev@sethm.id.au>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/process_madvise.2: HISTORY: ffix

Signed-off-by: Seth McDonald <dev@sethm.id.au>
Message-ID: <e0ecd2307cf922ec0a7ad34d6524f0a62bfc67e0.1771750388.git.dev@sethm.id.au>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/perfmonctl.2: HISTORY: wfix

Signed-off-by: Seth McDonald <dev@sethm.id.au>
Message-ID: <5be05e964e1443e036e18acbb8c497052d524259.1771750388.git.dev@sethm.id.au>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/open_tree.2: HISTORY: ffix

Signed-off-by: Seth McDonald <dev@sethm.id.au>
Message-ID: <3b27c0e095e33180f26181043f64f1a52a6066e8.1771750388.git.dev@sethm.id.au>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/: Use strnul(3) where suitable

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/: Use streq(3) where suitable

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strnul.3: SYNOPSIS: Document that it's a const-generic API

Document it as two overloads (C++-style).

Reported-by: Paul Eggert <eggert@cs.ucla.edu>
Suggested-by: Bruno Haible <bruno@clisp.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man3/strnul.3: New page

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/futex_waitv.2: Move text from ERRORS to DESCRIPTION

Signed-off-by: Alejandro Colomar <alx@kernel.org>

man/man2/futex_waitv.2: NOTES: Remove section

The previous commit made it redundant; I forgot to remove it then.

Fixes: eb7620b01fce (2026-02-18; "man/man2/futex_waitv.2: Move text from ERRORS to DESCRIPTION")
Signed-off-by: Alejandro Colomar <alx@kernel.org>