src-test2/lib, branch masterFreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=master2020-12-19T14:54:28Zlibc: Fix most issues reported by mandoc2020-12-19T14:54:28ZGordon Berglinggbe@FreeBSD.org2020-12-19T14:54:28Zurn:sha1:f6d234d8706fa4ad513bb5db2976b0e354a0f0fe
- varios "new sentence, new line" warnings
- varios "sections out of conventional order" warnings
- varios "unusual Xr order" warnings
- varios "missing section argument" warnings
- varios "no blank before trailing delimiter" warnings
- varios "normalizing date format" warnings
MFC after: 1 month
strerror.3: Fix whitespace issue introduced in r3687142020-12-18T22:10:17ZJessica Clarkejrtc27@FreeBSD.org2020-12-18T22:10:17Zurn:sha1:ccb86b40c172e14b454b44ca52750c24939355ea
MFC with: 368714
strerror.3: Add an example for perror()2020-12-17T12:41:47ZMateusz Piotrowski0mp@FreeBSD.org2020-12-17T12:41:47Zurn:sha1:87394cdd011a57807fe044046476981f2b0142c2
This is a nice and quick reference.
Reviewed by: jilles, yuripv
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D27623
nl_langinfo(3): document recognized item names2020-12-17T02:33:52ZYuri Pankovyuripv@FreeBSD.org2020-12-17T02:33:52Zurn:sha1:3cd6e2390cae6395f0a873612818cb7ee4a1749e
While here, remove .Tn macro usage (prompted by mandoc lint).
PR: 251468
Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D27606
Implement strerror_l().2020-12-16T09:02:09ZKonstantin Belousovkib@FreeBSD.org2020-12-16T09:02:09Zurn:sha1:675079b1ea61b310f3a42cb0d352a49c1780f89a
Only for the arches that provide user-mode TLS.
PR: 251651
Requested by: yuri
Discussed with: emaste, jilles, tijl
Sponsored by: The FreeBSD Foundation
Differential revision: https://reviews.freebsd.org/D27495
MFC after: 2 weeks
Be bug compatible with other operating systems by allowing non-sequential2020-12-14T11:56:16ZHans Petter Selaskyhselasky@FreeBSD.org2020-12-14T11:56:16Zurn:sha1:10557931153c8e347251b95418fe0f45dc2262dd
interface numbering for USB descriptors in userspace. Else certain USB
control requests using the interface number, won't be recognized by the
USB firmware.
Refer to section 9.2.3 in the USB 2.0 specification:
Interfaces are numbered from zero to one less than the number of concurrent interfaces
supported by the configuration.
PR: 251784
MFC after: 1 week
Sponsored by: Mellanox Technologies // NVIDIA Networking
strdup.3: Function appeared in 4.3BSD-Reno, not 4.4BSD2020-12-14T00:50:45ZJessica Clarkejrtc27@FreeBSD.org2020-12-14T00:50:45Zurn:sha1:87973534d2d67df59309d206a18fbdb256b589dd
Linux claims 4.3BSD, we claim 4.4BSD and OpenBSD claims 4.3BSD-Reno. It turns
out that OpenBSD got it right: the function was added in late 1988 a few months
after 4.3BSD-Tahoe, well in advance of 4.3BSD-Reno.
Reviewed by: bcr
Approved by: bcr
Differential Revision: https://reviews.freebsd.org/D27392
MFV r368607:2020-12-13T16:26:37ZMartin Matuskamm@FreeBSD.org2020-12-13T16:26:37Zurn:sha1:87c1ec0a31cce6441c52f6101d99482e50aeffba
Sync libarchive with vendor.
Vendor changes:
Issue #1461: Unbreak build without lzma
Issue #1462: warc reader: Fix build with gcc11
Issue #1463: Fix code compatibility in test_archive_read_support.c
Issue #1464: Use built-in strnlen on platforms where not available
Issue #1465: warc reader: fix undefined behaviour in deconst() function
MFC after: 3 days
X-MFC-With: 368234
Change getlocalbase() to not allocate any heap memory2020-12-12T11:23:52ZStefan Eßerse@FreeBSD.org2020-12-12T11:23:52Zurn:sha1:6c2596f00c26085ed9e3544a415f5f275c41eaec
After the commit of the current version, Scott Long pointed out, that an
attacker might be able to cause a use-after-free access if this function
returned the value of the sysctl variable "user.localbase" by freeing
the allocated memory without the cached address being cleared in the
library function.
To resolve this issue, I have proposed the originally suggested version
with a statically allocated buffer in a review (D27370). There was no
feedback on this review and after waiting for more than 2 weeks, the
potential security issue is fixed by this commit. (There was no security
risk in practice, since none of the programs converted to use this
function attempted to free the buffer. The address could only have
pointed into the heap if user.localbase was set to a non-default value,
into r/o data or the environment, else.)
This version uses a static buffer of size LOCALBASE_CTL_LEN, which
defaults to MAXPATHLEN. This does not increase the memory footprint
of the library at this time, since its data segment grows from less
than 7 KB to less than 8 KB, i.e. it will get two 4 KB pages on typical
architectures, anyway.
Compiling with LOCALBASE_CTL_LEN defined as 0 will remove the code
that accesses the sysctl variable, values between 1 and MAXPATHLEN-1
will limit the maximum size of the prefix. When built with such a
value and if too large a value has been configured in user.localbase,
the value defined as ILLEGAL_PREFIX will be returned to cause any
file operations on that result to fail. (Default value is "/dev/null/",
the review contained "/\177", but I assume that "/dev/null" exists and
can not be accessed as a directory. Any other string that can be assumed
not be a valid path prefix could be used.)
I do suggest to use LOCALBASE_CTL_LEN to size the in-kernel buffer for
the user.localbase variable, too. Doing this would guarantee that the
result always fit into the buffer in this library function (unless run
on a kernel built with a different buffer size.)
The function always returns a valid string, and only in case it is built
with a small static buffer and run on a system with too large a value in
user.localbase, the ILLEGAL_PREFIX will be returned, effectively causing
the created path to be non-existent.
Differential Revision: https://reviews.freebsd.org/D27370
timespec_get(3): sort SEE ALSO correctly2020-12-11T02:22:42ZEnji Cooperngie@FreeBSD.org2020-12-11T02:22:42Zurn:sha1:d03bd62f313209c99641381c35a65fc5f568c5b3
clock_gettime(2) should be mentioned before gettimeofday(2).
Reported by: make manlint
MFC after: 1 week
Sponsored by: DellEMC Isilon