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.
|r357995||lwhsu||Feb. 16, 2020, 10:57 a.m.||Remove trailing whitespace
Sponsored by: The FreeBSD FoundationViewVC
|r357991||mjg||Feb. 16, 2020, 3:33 a.m.||vfs: fix vlrureclaim ->v_object access
The routine was checking for ->v_type == VBAD. Since vgone drops the interlock early sets this type at the end of the process of dooming a vnode, this opens a time window where it can clear the pointer while the inerlock-holders is accessing it. Another note is that the code was: (vp->v_object != NULL && vp->v_object->resident_page_count > trigger) With the compiler being fully allowed to emit another read to get the pointer, and in fact it did on the kernel used by pho. Use atomic_load_ptr and remember the result. Note that this depends on type-safety of vm_object. Reported by: phoViewVC
|r357990||mjg||Feb. 16, 2020, 3:16 a.m.||vfs: check early for VCHR in vput_final to short-circuit in the common case
Otherwise the compiler inlines v_decr_devcount which keps getting jumped over in the common case of not dealing with a device.ViewVC
|r357989||mjg||Feb. 16, 2020, 3:14 a.m.||refcount: add missing release fence to refcount_release_if_gt
The CPU succeeding in releasing the not last reference can still have pending stores to the object protected by the affected counter. This opens a time window where another CPU can release the last reference and free the object, resulting in use-after-free. On top of that this prevents the compiler from generating more accesses to the object regardless of how atomic_fcmpset_rel_int is implemented (of course as long as it provides the release semantic). Reviewed by: markjViewVC
|r357988||jeff||Feb. 16, 2020, 1:07 a.m.||Slightly restructure uma_zalloc* to generate better code from clang and|
|r357987||mmacy||Feb. 16, 2020, 12:12 a.m.||Add zfree to zero allocation before free
Key and cookie management typically wants to avoid information leaks by explicitly zeroing before free. This routine simplifies that by permitting consumers to do so without carrying the size around. Reviewed by: jeff@, jhb@ MFC after: 1 week Sponsored by: Rubicon Communications, LLC (Netgate) Differential Revision: https://reviews.freebsd.org/D22790ViewVC
|r357986||mmacy||Feb. 16, 2020, 12:03 a.m.||Add chacha20poly1305 support to crypto build|
|r357985||kib||Feb. 15, 2020, 11:25 p.m.||Add pthread_peekjoin_np(3).|
|r357984||kib||Feb. 15, 2020, 11:19 p.m.||sem_remove(): fix the loop that compacts sem array on semaphores removal.|
|r357983||kib||Feb. 15, 2020, 11:18 p.m.||sem_remove(): add some asserts.|
|r357982||kib||Feb. 15, 2020, 11:15 p.m.||Use designated initializers for seminfo.|
|r357981||mjg||Feb. 15, 2020, 9:48 p.m.||ufs: use faster lockgmr entry points in ffs_lock|
|r357980||kevans||Feb. 15, 2020, 9:21 p.m.||committers-ports.dot: add myself as a ports committer|
|r357979||kevans||Feb. 15, 2020, 7:47 p.m.||fetch(3): don't leak sockshost on failure
fetch_socks5_getenv will allocate memory for the host (or set it to NULL) in all cases through the function; the caller is responsible for freeing it if we end up allocating. While I'm here, I've eliminated a label that just jumps to the next line...ViewVC
|r357978||kevans||Feb. 15, 2020, 7:39 p.m.||fetch(3): fix regression in IPv6:port spec from r357977
In case the port was specified, we never actually populated *host. Do so now. Pointy hat: kevansViewVC