According to IEEE 754 - 2008 , section 3.3, table 3.2
<https://irem.univ-reunion.fr/IMG/pdf/ieee-754-2008.pdf>
the value of emax is described as
emax = +127 / +1023
<https://en.wikipedia.org/wiki/IEEE_754#Basic_and_interchange_formats>
states the same values.
Also, to be more precise about the number of mantissa bits,
clarify that the implicit bit is included in the count.
Reported-by: "Dr. Wolfgang Armbruster" <dr.w.e.armbruster@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Jakub Sitnicki [Mon, 25 Apr 2022 16:08:03 +0000 (18:08 +0200)]
bpf.2: Note that unused fields and padding in bpf_attr must be zero
In a discussion regarding a potential backward incompatible change [1],
Andrii Nakryiko points out that unused bytes of bpf_attr should be
zero. Add this bit of information to the bpf(2) man page.
Axel Rasmussen [Tue, 12 Apr 2022 19:56:31 +0000 (12:56 -0700)]
ioctl_userfaultfd.2, userfaultfd.2: add minor fault mode
Userfaultfd minor fault mode is supported starting from Linux 5.13.
This commit adds a description of the new mode, as well as the new ioctl
used to resolve such faults. The two go hand-in-hand: one can't resolve
a minor fault without continue, and continue can't be used to resolve
any other kind of fault.
v1->v2:
- Some spelling / phrasing improvements
v2->v3:
- Improved line wrapping in man2/ioctl_userfaultfd.2
v3->v4:
- Rebased onto http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/ main
- Mentioned minor fault shmem support
- Improved line wrapping in man2/userfaultfd.2
Reviewed-by: Peter Xu <peterx@redhat.com> Signed-off-by: Axel Rasmussen <axelrasmussen@google.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
ISO C2x:
<http://www.open-std.org/JTC1/SC22/WG14/www/docs/n2731.pdf#subsubsection.7.21.6.2>
Still, from the documentation linked above, it seems to me that
"%Ln" is supported as a glibc extension, and doesn't fall into
"either no effect or undefined behavior" as says the GCC warning
shown in the bugzilla report. I didn't modify the documentation
regarding %n, and recommend investigating a possible GCC bug.
uri.7: The term URL is deprecated, in favor of URI
See RFCs 4395 (obsoleted by 7595) and 7595.
So, since URI and URL have been used as synonims and it wasn't
clear to most people what the difference was, the RFCs seem to
have explicitly avoided URL, and now use URI as the only term,
which still means what it meant (so now URL is just a synonim for
URI).
This commit replaces (almost all) occurences of URL by URI,
except when it is referring to the old term itself. Keep some
legacy info just for readers to understand this.
Cc: NGINX Unit <unit@nginx.org> Cc: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Ian Abbott [Fri, 18 Mar 2022 19:13:43 +0000 (19:13 +0000)]
ioctl_userfaultfd.2: Corrections for returned .ioctls members
Support for the `UFFDIO_WRITEPROTECT` operation is not indicated in the
`ioctls` member of `struct uffdio_api`. It is indicated in the `ioctls`
member of `struct uffdio_register` along with indications of support for
the `UFFDIO_COPY`, `UFFDIO_WAKE` and `UFFDIO_ZEROPAGE` operations (and
also the `UFFDIO_CONTINUE` operation supported since Linux 5.13 but
that is not documented by this man page yet.)
Fixes: f559fa36a678 ("ioctl_userfaultfd.2: Add write-protect mode docs") Signed-off-by: Ian Abbott <abbotti@mev.co.uk> Acked-by: Peter Xu <peterx@redhat.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
nick black [Mon, 21 Mar 2022 08:30:05 +0000 (04:30 -0400)]
console_codes.4: ffix
Fix up the busted OSC command list (reset palette and
set palette). Remove CSI prefix from the list of non-CSI
escapes. End all items of said list with periods,
matching other sections of the page.
Link: <https://lore.kernel.org/linux-man/Yjg4VHMhrabggl88@schwarzgerat.orthanc/T/> Signed-off-by: nick black <nickblack@linux.com> Acked-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Makefile: Remove old 'check-groff-warnings' target
Use 'lint-groff' instead, which show the same groff(1) warnings,
but also shows more warnings (CHECKSTYLE). It also runs
incrementally, so it only reruns for modified pages.
Makefile, etc/groff/tmac/deadly.tmac: Add lint and lint-groff targets
'lint' is a metatarget that triggers all lint-* targets (currently
that is just 'lint-groff').
'lint-groff' is a target that runs groff -rCHECKSTYLE to check
manual pages' groff(7) correctness.
etc/groff/tmac/deadly.tmac is a file written by Branden, to make
groff(1) abort when it finds a style problem, which then causes
make(1) to also abort.
Makefile: Use the $(V).SILENT trick instead of --silent
Hardcoding --silent into MAKEFLAGS makes it impossible to print
the commands used while running make. Instead, use the special
target .SILENT, masked by a dummy variable V, which when given any
value (e.g., V=1) will make the target non-special, and will not
silence the make invocation.
MADV_COLD and MADV_PAGEOUT advises on an address range which includes
locked, Huge TLB pages or VM_PFNMAP pages can return EINVAL. Update the
man pages accordingly.
Pádraig Brady [Mon, 14 Mar 2022 23:09:56 +0000 (23:09 +0000)]
stat.2, statx.2: Fix descriptions for AT_NO_AUTOMOUNT
fstatat(..., AT_NO_AUTOMOUNT) has had the following history in Linux: v2.6.37-7314-g6f45b65672c8
add AT_NO_AUTOMOUNT and fstatat honors it v3.1-rc7-68-gb6c8069d3577
ignore AT_NO_AUTOMOUNT since default operation now less eagerly mounts v4.10-11255-ga528d35e8bfc
adds statx which reinstated 2.6.38 behavior for fstatat (not released) v4.11-rc7-14-gdeccf497d804
adjust fstatat so that AT_NO_AUTOMOUNT always specified (to statx)
* man2/stat.2:
Adjust AT_NO_AUTOMOUNT description for fstatat.2 as per the above,
to indicate AT_NO_AUTOMOUNT should be avoided with fstatat() since
it's ignored since 3.1 and implied since 4.11.
Don't mention commit v4.13-9318-g42f461482178 as it was reverted,
and moot anyway since we can't adjust AT_NO_AUTOMOUNT since 3.1.
* man2/statx.2:
Mention that stat(), lstat(), and fstatat() imply AT_NO_AUTOMOUNT.
With only the default debug level documented, neither the possible
range of the debug levels nor their purpose was apparent. This made it
hard to use debug levels. So we add a short description of them.
Signed-off-by: Christian Aistleitner <christian@quelltextlich.at> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>