committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r363066||kevans||July 10, 2020, 12:45 a.m.||memfd_create: turn on SHM_GROW_ON_WRITE|
|r363065||kevans||July 10, 2020, 12:43 a.m.||shm_open2: Implement SHM_GROW_ON_WRITE
Lack of SHM_GROW_ON_WRITE is actively breaking Python's memfd_create tests, so go ahead and implement it. A future change will make memfd_create always set SHM_GROW_ON_WRITE, to match Linux behavior and unbreak Python's tests on -CURRENT. Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D25502ViewVC
|r363064||eugen||July 10, 2020, 12:24 a.m.||Optimize install(1) a bit.
Currently, "install -s -S" behaviour is inefficient for upgrade. First it finds that destination file already exists and copies source file to temporary file. Then it calls strip(1) with name of temporary file as single agrument and our strip(1) creates another temporary file in the /tmp (or TMPDIR) making another copy that is finally copied to DESTDIR third time. Meantime, strip(1) has an option "-o dst" to specify destination so install(1) is allowed to skip initial copying from obj to DESTDIR. This change makes it do so. Take a look at https://reviews.freebsd.org/D25551 for details and efficiency numbers (in short: upto 32% gained for installword). MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D25551ViewVC
|r363063||imp||July 10, 2020, 12:24 a.m.||Properly backout r362998|
|r363062||kevans||July 10, 2020, 12:03 a.m.||shmfd: make shm_size a vm_ooffset_t
On 32-bit platforms, this expands the shm_size to a 64-bit quantity and resolves a mismatch between the shmfd size and underlying vm_object size. The implementation did not account for this kind of mismatch. Reviewed by: kib MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D25602ViewVC
|r363061||cy||July 9, 2020, 11:01 p.m.||Enable support for IEEE 802.11N, 802.11W, 802.11AC and 802.11.AX to
hostapd and wpa_supplicant. Submitted by: bz MFC after: 2 weeks Relnotes: yes Sponsored by: Rubicon Communications, LLC (d/b/a "Netgate")ViewVC
|r363060||scottl||July 9, 2020, 10:38 p.m.||Revert r362998, r326999 while a better compatibility strategy is devised.|
|r363057||jilles||July 9, 2020, 8:53 p.m.||sh: Do not ignore INTOFF during a trap
INTOFF postpones SIGINT processing and INTON enables it again. This is important so an interactive shell can return to the top level prompt when Ctrl+C is pressed. Given that INTON is automatically done when a builtin completes, the part where onsig() ignores suppressint when in_dotrap is true is both unnecessary and unsafe. If the trap is for some other signal than SIGINT, arbitrary code could have been interrupted. Historically, INTOFF remained in effect for longer. Reviewed by: bdrewery MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D25270ViewVC
|r363055||markj||July 9, 2020, 6:34 p.m.||Apply the logic from r363051 to semctl(2) and __sem_base field.|
|r363052||markj||July 9, 2020, 5:27 p.m.||whois: Handle referrals to rwhois servers.|
|r363051||markj||July 9, 2020, 5:26 p.m.||Avoid copying out kernel pointers from msgctl(IPC_STAT).
While this behaviour is harmless, it is really just an artifact of the fact that the msgctl(2) implementation uses a user-visible structure as part of the internal implementation, so it is not deliberate and these pointers are not useful to userspace. Thus, NULL them out before copying out, and remove references to them from the manual page. Reported by: Jeffball <email@example.com> Reviewed by: emaste, kib MFC after: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D25600ViewVC
|r363047||andrew||July 9, 2020, 4:28 p.m.||Add a driver to talk to the Raspberry Pi firmware
Communicating with the Raspberry Pi firmware is currently handled by each driver calling into the mbox driver, however the device tree is structured such that they should be calling into a firmware driver. Add a driver for this node with an interface to communicate to the firmware via the mbox interface. There is a sysctl to get the firmware revision. This is a unix date so can be parsed with: root@generic:~ # date -j -f '%s' sysctl -n dev.bcm2835_firmware.0.revision Tue Nov 19 16:40:28 UTC 2019 Reviewed by: manu Sponsored by: Innovate UK Differential Revision: https://reviews.freebsd.org/D25572ViewVC
|r363046||tuexen||July 9, 2020, 4:18 p.m.||Optimize flushing of receive queues.
This addresses an issue found and reported for the userland stack in https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21243 MFC after: 1 weekViewVC
|r363042||tsoome||July 9, 2020, 1:19 p.m.||loader: setting vdev size based on label asize is not working|
|r363036||delphij||July 9, 2020, 8 a.m.||g_concat_find_device: trim /dev/ if it is present, like other GEOM|