FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F13.3 2023-08-23T17:43:32Z 2023-08-23T17:43:32Z Warner Losh imp@FreeBSD.org 2023-08-22T01:32:14Z urn:sha1:27096e41f03f81fd6622e45ec3a91268f0eacdc8 Remove /^\s*\$FreeBSD\$$\n/ Similar commit in current: (cherry picked from commit 78d146160dc5) 2023-08-23T17:43:22Z Warner Losh imp@FreeBSD.org 2023-08-22T01:31:09Z urn:sha1:4b40a16f0d188422227478889b38cc341d50f88f Remove /^\s*\*+\s*\$FreeBSD\$.*$\n/ Similar commit in current: (cherry picked from commit 2ff63af9b88c) 2023-07-25T15:13:49Z Warner Losh imp@FreeBSD.org 2023-05-10T15:40:58Z urn:sha1:caa41f641755c935b036e17440a3b49329c904ed The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause. Discussed with: pfg MFC After: 3 days Sponsored by: Netflix (cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b) 2022-04-11T03:39:10Z Gordon Bergling gbe@FreeBSD.org 2022-04-06T16:27:29Z urn:sha1:d9d5b117972ee3c86a97c291eaa0cb38048e631a - s/mulitplexor/multiplexor/ (cherry picked from commit f64919bbd9b7d84f61a99264c33187fc63aca2a4) 2021-08-11T01:54:00Z Roy Marples roy@marples.name 2021-07-28T15:46:59Z urn:sha1:f45271340836769d53320d6dbcf63226bb4e39e3 SO_RERROR indicates that receive buffer overflows should be handled as errors. Historically receive buffer overflows have been ignored and programs could not tell if they missed messages or messages had been truncated because of overflows. Since programs historically do not expect to get receive overflow errors, this behavior is not the default. This is really really important for programs that use route(4) to keep in sync with the system. If we loose a message then we need to reload the full system state, otherwise the behaviour from that point is undefined and can lead to chasing bogus bug reports. Reviewed by: philip (network), kbowling (transport), gbe (manpages) MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D26652 (cherry picked from commit 7045b1603bdf054145dd958a4acc17b410fb62a0) 2021-06-21T13:14:40Z Mark Johnston markj@FreeBSD.org 2021-06-14T21:32:27Z urn:sha1:46d8116cae6845be70230640f16568576269b177 Some code was using it already, but in many places we were testing SO_ACCEPTCONN directly. As a small step towards fixing some bugs involving synchronization with listen(2), make the kernel consistently use SOLISTENING(). No functional change intended. Sponsored by: The FreeBSD Foundation (cherry picked from commit f4bb1869ddd2bca89b6b6bfaf4d866efdd9243cf) 2020-09-01T21:19:14Z Mateusz Guzik mjg@FreeBSD.org 2020-09-01T21:19:14Z urn:sha1:662c13053f4bf2d6245ba7e2b66c10d1cd5c1fb9 2020-07-01T04:00:54Z Takanori Watanabe takawata@FreeBSD.org 2020-07-01T04:00:54Z urn:sha1:263a104f435ed2742dc6ed926278d422527d482f PR: 247588 Reported by: Greg V (greg@unrelenting.technology) Reviewed by: emax Differential Revision: https://reviews.freebsd.org/D25516 2020-02-26T14:26:36Z Pawel Biernacki kaktus@FreeBSD.org 2020-02-26T14:26:36Z urn:sha1:7029da5c36f2d3cf6bb6c81bf551229f416399e8 r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes. This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags. Mark all obvious cases as MPSAFE. All entries that haven't been marked as MPSAFE before are by default marked as NEEDGIANT Approved by: kib (mentor, blanket) Commented by: kib, gallatin, melifaro Differential Revision: https://reviews.freebsd.org/D23718 2019-08-30T16:35:31Z Maksim Yevmenkin emax@FreeBSD.org 2019-08-30T16:35:31Z urn:sha1:444e5d09b56876803cd4ed3c13c8ed9d9e3a2c65 Reported by: imp, mms dot vanbreukelingen at gmail dot com Reviewed by: imp