committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|2c7a6dad||kib||Oct. 21, 2021, 12:09 a.m.||ldd: do not use dlopen(RTLD_TRACE) for dso when format is specified
Problem is that rtld cannot reliably access updated environment. This was made more obvious by bfd4c875a10560aaa2. The application environment can be in arbitrary state and place, system components can observe it only during execve(2), or in case of rtld, right after execve, when environment is still at know location and format. Instead spawn ld-elf.so.1 in direct exec mode which can correctly read all inherited updates to the environment. PR: 259069 Reviewed by: arichardson, jhb Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D32464cgit
|ca8c576d||kib||Oct. 21, 2021, 12:09 a.m.||ldd: style|
|33dba3bb||kib||Oct. 21, 2021, 12:08 a.m.||rtld-elf/paths.h: Make it usable outside rtld
but still for tightly coupled things like ldd(1) Rename paths.h to rtld_paths.h. Add guard for rtld-specific externs declarations. Add _COMPAT32_BASENAME_RTLD and _COMPAT32_PATH_RTLD. Reviewed by: arichardson, jhb Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D32464cgit
|9ce201f2||asomers||Oct. 21, 2021, 12:05 a.m.||ping: fix parsing of options including '4' and '6'
ping uses a two-pass option parser. The first pass determines whether ipv4 or ipv6 is desired, and the second parses the rest of the options. But the first pass wrongly detects a '4' or '6' in an option's value as a request to use ipv6 or ipv6 respectively, for example in an invocation like "ping -c6 220.127.116.11". Fix this confusion by including all options in the first round of parsing, but ignoring those unrelated to ipv4/ipv6 selection. PR: 258048 Reported by: firstname.lastname@example.org Submitted by: email@example.com MFC after: 2 weeks Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D32344cgit
|5c534010||emaste||Oct. 20, 2021, 11:25 p.m.||net: Allow binding of unspecified address without address existance
Previously in_pcbbind_setup returned EADDRNOTAVAIL for empty V_in_ifaddrhead (i.e., no IPv4 addresses configured) and in6_pcbbind did the same for empty V_in6_ifaddrhead (no IPv6 addresses). An equivalent test has existed since 4.4-Lite. It was presumably done to avoid extra work (assuming the address isn't going to be found later). In normal system operation *_ifaddrhead will not be empty: they will at least have the loopback address(es). In practice no work will be avoided. Further, this case caused net/dhcpd to fail when run early in boot before assignment of any addresses. It should be possible to bind the unspecified address even if no addresses have been configured yet, so just remove the tests. The now-removed "XXX broken" comments were added in 59562606b9d3, which converted the ifaddr lists to TAILQs. As far as I (emaste) can tell the brokenness is the issue described above, not some aspect of the TAILQ conversion. PR: 253166 Reviewed by: ae, bz, donner, emaste, glebius MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D32563cgit
|f8328864||luporl||Oct. 20, 2021, 6:48 p.m.||powerpc64le: stand fixes
Fix boot1 and loader on PowerPC64 little-endian (LE). Due to endian issues, boot1 couldn't find the UFS boot partition and loader wasn't able to load the kernel. Most of the issues happened because boot1 and loader were BE binaries trying to access LE UFS partitions and because loader expects the kernel ELF image to use the same endian as itself. To fix these issues, boot1 and loader are now built as LE binaries on PPC64LE. To support this, the functions that call OpenFirmware were enhanced to correctly perform endian conversion on its input and output arguments and to change the CPU into BE mode before making the calls, as OpenFirmware always runs in BE. Besides that, some other small fixes were needed. Submitted by: bdragon (initial version) Reviewed by: alfredo, jhibbits Sponsored by: Instituto de Pesquisas Eldorado (eldorado.org.br) Differential Revision: https://reviews.freebsd.org/D32160cgit
|2ff7c2cc||kib||Oct. 20, 2021, 6:29 p.m.||sys/bus.h: silence warnings about write-only variables|
|2bd6d910||kib||Oct. 20, 2021, 6:29 p.m.||msdosfs_rename: remove write-only variables|
|80bca63c||kib||Oct. 20, 2021, 6:29 p.m.||tmpfs: remove write-only variables|
|2a213a2e||bapt||Oct. 20, 2021, 12:18 p.m.||OptionalObsoleteFiles: add more googletest files to remove|
|f3aad18d||bapt||Oct. 20, 2021, noon||sh(1): fix home/del key on mobaxterm env
For $reason mobaxterm default on sending unusual sequence from home/del key, which makes libedit unabel to catch them and bind them correctly. mobaxterm seems popular on the windows environment, so add proper keybinding to default shrc configuration so it works out of box. Reported by: lmecgit
|4fb00280||andrew||Oct. 20, 2021, 10:02 a.m.||Pass the ACPI ID when reading the ACPI domain
The ACPI ID may not be the same as the FreeBSD CPU id. Use the former when finding the CPU domain as there is no requirement for it to be identical to the latter. Reported by: dch, kevans Reviewed by: kevans Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D32546cgit
|5fe97373||bapt||Oct. 20, 2021, 9:23 a.m.||skel: update .shrc as well
Somehow we end up having 2 definition of the same .shrc in the source tree, both of them should have been updated. A batter fix would be to only keep one copy of the same file. but that would be for another commit Reported by: lmecgit
|3f550f01||bapt||Oct. 20, 2021, 8:44 a.m.||timeout: style fixes|
|68914dab||bapt||Oct. 20, 2021, 8:39 a.m.||timeout: eliminate usage of sysexits
It brings no value at all the sysexits and maybe misleading as the return value of timeout(1) matters.cgit