b8135ed6 0mp Nov. 18, 2021, 2:56 p.m.
B is listed as an interactive command to toggle the display of threads.
This is a typo introduced during the conversion of the manual page to
mdoc.

Fixes:		9d6cce02a78c967e69b603d503545c4b43d7765f
MFC after:	3 days
cgit
0d7a6199 kib Nov. 18, 2021, 1:56 p.m.
Print some warning when export is requested for non-existing symbol.

Reviewed by:	emaste
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D32878
cgit
a7e4eb14 kib Nov. 18, 2021, 1:56 p.m.
Reviewed by:	emaste
Sponsored by:	The FreeBSD Foundation
MFC after:	3 days
Differential revision:	https://reviews.freebsd.org/D32878
cgit
5bb3134a kib Nov. 18, 2021, 1:56 p.m.
and remove non-present symbols that are now reported by kmod_syms.awk.

Reviewed by:	emaste
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D32878
cgit
3850d183 glebius Nov. 18, 2021, 8:54 a.m.
0dff875f glebius Nov. 18, 2021, 8:54 a.m.
50d7d967 royger Nov. 18, 2021, 8:46 a.m.
The current definition for the MMAP_RESOURCE ioctl was wrong as it
didn't copy back the result to the caller. Fix the definition and also
remove the bogus attempt to copy the result in the implementation.

Note such copy back is only needed when querying the size of a
resource.

Sponsored by: Citrix Systems R&D
cgit
4fdc5b84 kib Nov. 18, 2021, 3:02 a.m.
Sponsored by:	The FreeBSD Foundation
MFC after:	3 days
cgit
fea4a9af brooks Nov. 18, 2021, 1:02 a.m.
fspacectl(2) does not require special handling on freebsd32. The
presence of off_t in a struct does not cause it's size to change
between the native ABI and the 32-bit ABI supported by freebsd32
because off_t is always int64_t on BSD systems.  Further, byte
order only requires handling for paired argument or return registers.

(32-byte alignment of 64-bit objects on i386 can require special
handling, but that situtation does not apply here.)

Reviewed by:	kib, khng, emaste, delphij
Differential Revision:	https://reviews.freebsd.org/D32994
cgit
4082b189 jhb Nov. 17, 2021, 11:51 p.m.
Reviewed by:	kib
Obtained from:	CheriBSD
Sponsored by:	The University of Cambridge, Google Inc.
Differential Revision:	https://reviews.freebsd.org/D33052
cgit
19621645 jhb Nov. 17, 2021, 11:51 p.m.
Reviewed by:	kib
Obtained from:	CheriBSD
Sponsored by:	The University of Cambridge, Google Inc.
Differential Revision:	https://reviews.freebsd.org/D33051
cgit
8b2ce7a3 jhb Nov. 17, 2021, 11:51 p.m.
Reviewed by:	kib
Sponsored by:	The University of Cambridge, Google Inc.
Differential Revision:	https://reviews.freebsd.org/D33050
cgit
a8d88529 jhb Nov. 17, 2021, 11:51 p.m.
Reviewed by:	kib
Sponsored by:	The University of Cambridge, Google Inc.
Differential Revision:	https://reviews.freebsd.org/D33048
cgit
b928e924 jhb Nov. 17, 2021, 11:50 p.m.
Reviewed by:	kib
Sponsored by:	The University of Cambridge, Google Inc.
Differential Revision:	https://reviews.freebsd.org/D33047
cgit
201d0ebe mm Nov. 17, 2021, 9:28 p.m.
Vendor commit message (ede459d2e):
  archive_write_disk_posix: fix writing fflags broken in 8a1bd5c

  The fixup list was erroneously assumed to be directories only.
  Only in the case of critical file flags modification (e.g.
  SF_IMMUTABLE on BSD systems), other file types (e.g. regular files
  or symbolic links) may be added to the fixup list. We still need to
  verify that we are writing to the correct file type, so compare the
  archive entry file type with the file type of the file to be
  modified.

Fixes vendor issue #1617:
  Immutable flag no longer preserved during tar extraction on FreeBSD

MFC after:		3 days
Reported by:		markjdb
Libarchive commit:	ede459d2ebb879f5eedb6f7abea203be0b334230
cgit