share/mk/: Fix path

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

process_madvise.2: Fix comments about commit ids

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>

CONTRIBUTING.d/lint: Rewrite now that we have $SKIP_XFAIL

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

share/mk/, man*/: build-ex: Skip expected failures

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

etc/cppcheck/cppcheck.suppress: Silence report

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

share/mk/, etc/: Fix dependencies

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

share/mk/: lint-c: Skip expected failures

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

man3/: Say cancelation instead of cancellation

It's the most common spelling in this project.

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

share/mk/: $SKIP_XFAIL: Add variable to allow skipping expected failures

Default to 'yes'.

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

share/mk/: distcheck: string_copying.7 fails 'check-catman'

Except with groff(1) from git HEAD, which will be 1.24.0 eventually.

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

mbsrtowcs.3: ffix

With groff-1.23.0, which has a base paragraph indentation of 7, this
line was longer than 80 columns.

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

share/mk/configure/version.mk: $DISTDATECMD: Use committer date, not author date

Comitter date is always increasing, while author date may jump
backwards, which is problematic with make(1).

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

share/mk/: Simplify code

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

share/mk/: distcheck: Ignore fanotify_init.2 build errors

In groff from git HEAD, it doesn't fail, but in 1.23.0, which still
has the default base paragraph indentation set to 7, it reports

troff:man2/fanotify_init.2:322: warning [p 4, 0.7i]: cannot adjust line

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

man*/: srcfix

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*/: ffix

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>

share/mk/: distcheck-*: Add targets to run 'distcheck' partially

This is mainly for debugging purposes.  I won't document it in
'make help' for now, as it will clutter the output, and isn't so useful
for normal users.

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

vsock.7: ffix

Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

process_madvise.2: Rename parameter, and use array syntax

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

process_madvise.2: Document the glibc wrapper

$ 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 extensions

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-2001

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_dirent64

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>

share/mk/: srcfix

Use a variable for the options passed to recursive make(1), to avoid
repetition.

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

share/mk/: dist: Show CP instead of INSTALL

We're using install(1), but it's just an implementation detail.
Since we're not installing into the system, CP is less confusing.

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

share/mk/: dist: FORCE regeneration of version file if necessary

If any of $DISTVERSION, $DISTNAME, or $DISTDATE have changed since the
last 'make dist', force regeneration of the version file, even if it
wouldn't change due to normal dependencies.  This makes sure that the
tarball has correct values.

It doesn't need to depend on all $DISTFILES.

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

share/mk/: $DISTDATE: If the repository is "dirty", use the newest timestamp

Otherwise, the files within the 'dist' tarball will have a timestamp
older than their last actual modification, which is problematic with
'distcheck'.

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

share/mk/: dist: Preserve links with cp(1)

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

share/mk/: Consistently use 'cp -T'

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

share/mk/configure/version.mk: $DISTNAME: Pass --dirty to git-describe(1)

This makes sure we don't accidentally produce release tarballs from a
dirty repository.

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

share/mk/configure/version.mk: $DISTNAME: Don't hide git(1) errors

We don't call git(1) inside tarballs anymore to get the $DISTNAME, so we
can safely assume that git(1) should never fail, and if it fails, we
better get an error message.

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

share/mk/: distcheck: Remove old directory before untarring the new tarball

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

share/mk/: distcheck: Fix dependencies

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

share/mk/: Fix path

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

share/mk/: distcheck: Support an absolute path in $builddir

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

share/mk/: distcheck: Use temporary dirs within $builddir

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

close_range.2: srcfix

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

share/mk/: Use a variable to prefix recursive make(1) output

Piping the output to sed(1) didn't behave well with -Orecurse.  Using a
variable behaves well, keeping output synchronized.  The length of the
variable name is specific, so that `$(INFO_)` uses exactly 8 characters,
a tab.

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

GNUmakefile: help: Document 'distcheck'

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

close_range.2: Add _GNU_SOURCE and <unistd.h> to SYNOPSIS

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>

getaddrinfo.3: tfix

(Incidentally, the glibc function source does name the parameter
"name" rather than "node", unlike this man page.  (The POSIX man
page uses "nodename".))

Signed-off-by: Štěpán Němec <stepnem@smrk.net>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man*/: tfix

Signed-off-by: Štěpán Němec <stepnem@smrk.net>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

path_resolution.7: Work around groff(1) bug

Link: <https://savannah.gnu.org/bugs/?65320>
Link: <https://savannah.gnu.org/bugs/?65322>
Link: <https://lists.gnu.org/archive/html/groff/2024-02/msg00039.html>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

share/mk/: clean: Also remove 'distcheck' tmp dirs

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

share/mk/: $(info ...): Make output more consistent

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

share/mk/: Use $(TRUE) instead of ':'

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

share/mk/dist/: dist: Support recursive 'dist'

Hardcode the version and date, and don't use git(1) for selecting the
distribution files.

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

share/mk/: distcheck: Add target

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

share/mk/: Reorganize build system

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

share/mk/: Move configuration variables to share/mk/configure/

Some variables are only part of the implementation of our build system,
and users should not modify them; others are designed to be set by users
when they invoke make(1).  Define the latter in share/mk/configure/, so
that they are more visible.

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

share/mk/: Move '.SILENT:' to GNUmakefile

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

share/mk/: Reorganize build dependencies

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

.gitignore: Widen glob

There are other similar files generated by checkpatch.

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

Start of man-pages-NEXT: Move Changes to Changes.old

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

lsm: Released 6.06

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

Changes: Ready for 6.06

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

ld.so.8: srcfix

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

man*/: ffix

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

pthread_create.3: Re-do the architecture/default stack size mapping

Currently, the page lists 2 of the 3 x86 architectures, no ARM(!),
old PowerPC only, and most egregiously itanium,
which linux doesn't target.

Per glibc 2.38:
  $ git grep ARCH_STACK_DEFAULT_SIZE
  aarch64     #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  arc         #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  arm         #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  csky        #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  loongarch   #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  m68k        #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  microblaze  #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  mips        #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  nios2       #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  or1k        #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  riscv       #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  s390        #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  sh          #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  sparc32     #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)
  x86         #define ARCH_STACK_DEFAULT_SIZE  (2 * 1024 * 1024)

  alpha       #define ARCH_STACK_DEFAULT_SIZE  (4 * 1024 * 1024)
  powerpc     #define ARCH_STACK_DEFAULT_SIZE  (4 * 1024 * 1024)
  sparc64     #define ARCH_STACK_DEFAULT_SIZE  (4 * 1024 * 1024)

  hppa        #define ARCH_STACK_DEFAULT_SIZE  (8 * 1024 * 1024)

  ia64        #define ARCH_STACK_DEFAULT_SIZE (32 * 1024 * 1024)

I cut PA-RISC and the Alpha. They have 10 and 6 popcon entries,
respectively, and AFAICT they haven't seen a processor released
in over a decade, they aren't relevant to any modern reader.

Similarly, use "POWER" instead of "PowerPC" ‒ the consensus branding
is "POWER"+version (POWER8/POWER9); PowerPC is itself a POWER variant
and doesn't really deserve its own special mention, especially in 2024.

Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

seteuid.2: glibc implements seteuid() calling setresuid(), not setreuid()

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>

README: Use <kernel.org> URL

<https://kernel.org/pub/> is redirected to
<https://mirrors.edge.kernel.org/pub/>, but it's better not rely on that
and use the primary URL.

Signed-off-by: Petr Vorel <pvorel@suse.cz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING, CONTRIBUTING.d/mail: Split file, and rewrite CONTRIBUTING as an intro

CONTRIBUTING is now an intro to all the files in CONTRIBUTING.d/

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

CONTRIBUTING, CONTRIBUTING.d/patches: Split CONTRIBUTING file

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

CONTRIBUTING, CONTRIBUTING.d/style: Split CONTRIBUTING file

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

CONTRIBUTING, CONTRIBUTING.d/lint: Split CONTRIBUTING file

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

CONTRIBUTING, CONTRIBUTING.d/external_pages: Split CONTRIBUTING file

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

CONTRIBUTING, CONTRIBUTING.d/bugs, README: Split CONTRIBUTING file

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

CONTRIBUTING: neomutt(1) can now be used to sign patches

Link: <https://github.com/neomutt/neomutt/issues/1471>
Link: <https://github.com/neomutt/neomutt/pull/4134>
Link: <https://neomutt.org/feature/cli-crypto>
Cc: "G. Branden Robinson" <branden@debian.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

frexp.3: ISO C defines frexp(3) in terms of 2, not FLT_RADIX

Even in systems where FLT_RADIX != 2, frexp(3) would be 2-based.
This was correctly worded in the DESCRIPTION, but the example program
was incorrect.

Link: <https://lore.kernel.org/linux-man/CANv4PNkqQBPn_oyfdYZfOck-7gGwzP6YPPA9hDaiaJPUj+c3xw@mail.gmail.com/T/#u>
Reported-by: Morten Welinder <mwelinder@gmail.com>
Cc: Matthew House <mattlloydhouse@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

adjtime.3: wfix

Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

charsets.7: Say ISO/IEC 2375

Link: <https://www.iso.org/standard/32184.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man*/: Say ISO 3166

Link: <https://www.iso.org/iso-3166-country-codes.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

locale.5: Say ISO 4217

Link: <https://www.iso.org/standard/64758.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man*/: Say ISO 639

Link: <https://www.iso.org/standard/74575.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man*/: Say ISO/IEC 646

Link: <https://www.iso.org/standard/4777.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

filesystems.5: Say ISO/IEC 9660

Link: <https://www.iso.org/standard/81979.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man*/: Say ISO/IEC 8208

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*/: Say ISO/IEC 6429

Link: <https://www.iso.org/standard/12782.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man3/: Say ISO 8601

Link: <https://www.iso.org/standard/70907.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

nl_langinfo.3: ffix

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

man*/: Say ISO/IEC 8859

Link: <https://www.iso.org/standard/28245.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

man*/: Say ISO/IEC 2022

Link: <https://www.iso.org/standard/22747.html>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Cc: Mario Blaettermann <mario.blaettermann@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

charsets.7: Say ISO/IEC 4873

Link: <https://www.iso.org/standard/10859.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 line

It seems those dates were accidentally hardcoded.

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

*.mk: Allow pages with the suffix .man and no number

This adds support for neomutt.man from the neomutt project.

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

open.2: srcfix

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: ffix

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: wfix

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>

fts.3, div_t.3type: ffix

Break lines containing a parametric prefix to a man page name into two
lines, using distinct font alternation macros and the `\c` escape
sequence to "connect" the output.  This prepares for adoption of the
`MR` man(7) macro in groff 1.23.0.

The style seen here assumes that the typeface used for man page names is
bold, which is ahistorical and which the `MR` feature makes
configurable.  It might be better to recast this shorthand into English.

Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

socket.7: Mention CAP_NET_RAW on SO_MARK

Added in 079925cce1d0 ("net: allow SO_MARK with CAP_NET_RAW") in
Linux 5.17.

Cc: Maciej Żenczykowski <maze@google.com>
Cc: Matthias Gerstner <matthias.gerstner@suse.com>
Signed-off-by: Petr Vorel <pvorel@suse.cz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

locale.5: tfix

...that proved surprisingly tough to troubleshoot.

I got the following output from my working copy.

grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32291: error: output above first line discarded
grotty:...:(man5/locale.5):32292: error: output above first line discarded
grotty:...:(man5/locale.5):32294: error: output above first line discarded
grotty:...:(man5/locale.5):32294: error: output above first line discarded
grotty:...:(man5/locale.5):32294: error: output above first line discarded
grotty:...:(man5/locale.5):32294: error: output above first line discarded
grotty:...:(man5/locale.5):32294: error: output above first line discarded

`\r` is a perfectly legal *roff escape sequence, but one generally never
sees it in man pages.  In that case, the input line in question was at
the top of the "page" in continuous rendering mode, and so the attempt
at a reverse vertical motion did indeed put the drawing position above
the top of the page.

grepping reveals no other occurrences of '\r' in the man-pages corpus.

Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

cpuid.4: Note which CPUs don't support CPUID and what happens

"Early 486" comes from an uncited wikipedia table, added in
<https://en.wikipedia.org/w/index.php?title=CPUID&diff=prev&oldid=592047209>
<https://en.wikipedia.org/w/index.php?title=CPUID&diff=prev&oldid=592047978>
but I spot-checked the rest of the table accurate to CPUs in my house
(the oldest of which is an original Celeron, so no 486),
and "early 486" is better than "early x86" which can mean anything.

This does leave earlier x86 unmentioned,
but Linux hasn't targeted those in over a decade,
so they're out of scope anyway.

Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

sched_getcpu.3: tfix

Fixes: 2b65a83f2983 ("Documents sched_getcpu(3), a wrapper for getcpu(2), provided since glibc 2.6.")
Reported-by: Shahab Ouraie <shahabouraie@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

faccessat(2), utimensat(2): Document AT_EMPTY_PATH flag

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>

fopencookie.3, stdio.3: wfix

Suggested-by: Alejandro Colomar <alx@kernel.org>
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

stdio.3: Note down fmemopen(3), fopencookie(3), and open_[w]memstream(3)

I was looking for fmemopen() to remember I was actually looking for
open_memstream(), and it was much more difficult than it ought to've
been.

Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

open_memstream.3: ffix

Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING: Reduce strength of encouragement

That paragraph may be confusing to those who don't know about PGP, so
reduce strength of encouragement.  But to those that know about PGP, and
know how to use it, please, please use it.

Suggested-by: "G. Branden Robinson" <branden@debian.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

CONTRIBUTING: Accept patches in attachments

I use mutt(1), which works fine with patches as attachments, and the
mailing list archives also work fine with attachments.  Let's accept
attachments.

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

CONTRIBUTING: The Majordomo has been fired

The infrastructure of the list was recently modified.  Now, all the
information to subscribe, unsubscribe, or other actions, are in
<https://subspace.kernel.org/vger.kernel.org.html>.

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