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.
|a5ac8272||mjg||Nov. 22, 2018, 9:29 p.m.||fork: remove avoidable proc lock/unlock pair|
|b00b27e9||mjg||Nov. 22, 2018, 9:08 p.m.||fork: fix use-after-free with vfork
The pointer to the child is stored without any reference held. Then it is blindly used to wait until P_PPWAIT is cleared. However, if the child is autoreaped it could have exited and get freed before the parent started waiting. Use the existing hold mechanism to mitigate the problem. Most common case of doing exec remains unchanged. The corner case of doing exit performs wake up before waiting for holds to clear. Reviewed by: kib Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D18295cgit ViewVC
|79db6fe7||markj||Nov. 22, 2018, 8:49 p.m.||Plug some networking sysctl leaks.
Various network protocol sysctl handlers were not zero-filling their output buffers and thus would export uninitialized stack memory to userland. Fix a number of such handlers. Reported by: Thomas Barabosch, Fraunhofer FKIE Reviewed by: tuexen MFC after: 3 days Security: kernel memory disclosure Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D18301cgit ViewVC
|ad2be389||tuexen||Nov. 22, 2018, 8:05 p.m.||A TCP stack is required to check SEG.ACK first, when processing a|
|fef56019||tuexen||Nov. 22, 2018, 8:02 p.m.||Ensure that the TCP RACK stack honours the setting of the|
|7e729f07||tuexen||Nov. 22, 2018, 7:56 p.m.||Ensure that the default RTT stack can make an RTT measurement if
the TCP connection was initiated using the RACK stack, but the peer does not support the TCP RACK extension. This ensures that the TCP behaviour on the wire is the same if the TCP connection is initated using the RACK stack or the default stack. Reviewed by: rrs@ MFC after: 1 week Sponsored by: Netflix, Inc. Differential Revision: https://reviews.freebsd.org/D18032cgit ViewVC
|79410718||tuexen||Nov. 22, 2018, 7:49 p.m.||Ensure that TCP RST-segments announce consistently a receiver window of|
|2910a161||markj||Nov. 22, 2018, 5:51 p.m.||Clear unused bytes in ia32_osendsig().
Mirror the fix for the native i386 implementation from r218327. This code is compiled only when the non-default COMPAT_43 option is configured. Reported by: Ilja Van Sprundel <email@example.com> Reviewed by: kib MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D18298cgit ViewVC
|dc9874ea||emaste||Nov. 22, 2018, 4:55 p.m.||proto: change device permissions to 0600
C Turt reports that the driver is not thread safe and may have exploitable races. Note that the proto device is intended for prototyping and development, and is not for use on production systems. From the man page: SECURITY CONSIDERATIONS Because programs have direct access to the hardware, the proto driver is inherently insecure. It is not advisable to use this driver on a production machine. The proto device is not included in any of FreeBSD's kernel config files (although the module is built). The issues in the proto device still need to be fixed, and the device is inherently (and intentionally) insecure, but it might as well be limited to root only. admbugs: 782 Reported by: C Turt <firstname.lastname@example.org> MFC after: 3 days Sponsored by: The FreeBSD Foundationcgit ViewVC
|d343a7f4||arybchik||Nov. 22, 2018, 4:15 p.m.||sfxge(4): limit max TXQ size on Medford to 2048|
|8e0c4827||arybchik||Nov. 22, 2018, 2:31 p.m.||sfxge(4): support packed stream Rx mode in libefx|
|621cf621||arybchik||Nov. 22, 2018, 2:10 p.m.||sfxge(4): cleanup: move into right place|
|d19c1c8e||cy||Nov. 22, 2018, 4:48 a.m.||Allow forced start of ipmon in special cases where testing is desired|
|248b5d08||mjg||Nov. 21, 2018, 10:37 p.m.||strings: unbreak the build after r340746|
|f218ac50||mjg||Nov. 21, 2018, 10:25 p.m.||uipc_usrreq: fix inode number assignment
The code was incrementing a global variable in an unsafe manner. Two different threads stating two different sockets could have resulted in the same inode numbers assigned to both. Creation is protected with a global lock, move the assigment there. Since inode numbers are 64-bit now drop the check for overflows. Sponsored by: The FreeBSD Foundationcgit ViewVC