FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=releng%2F11.2 2018-03-05T07:26:05Z 2018-03-05T07:26:05Z Eitan Adler eadler@FreeBSD.org 2018-03-05T07:26:05Z urn:sha1:25d4b2c1b89d42d752e23f9935692f481cb272ea various: general adoption of SPDX licensing ID tags. Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task. The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts. No functional change intended. 2017-02-21T02:23:57Z Enji Cooper ngie@FreeBSD.org 2017-02-21T02:23:57Z urn:sha1:081b9ba142569a58def1bf4c6f95da812eb53594 Use SRCTOP to define .include with usr.bin/Makefile.inc 2015-12-01T05:18:48Z Bryan Drewery bdrewery@FreeBSD.org 2015-12-01T05:18:48Z urn:sha1:cf990407e1bde2ebf0ab8a34e28c38a08f076288 Unfortunately filemon/meta mode tracks all indirect dependencies here since ld(1) is reading libelf when linking in libkvm. Churn would be reduced if this was able to be limited to direct dependencies. Sponsored by: EMC / Isilon Storage Division 2015-09-01T06:28:16Z Xin LI delphij@FreeBSD.org 2015-09-01T06:28:16Z urn:sha1:0a107daff70338b78e4e977fa350c63d08daa56d would not drop privileges as expected. While there also add checks for the drop and bail out immediately if we failed. MFC after: 3 days 2015-06-13T19:20:56Z Simon J. Gerraty sjg@FreeBSD.org 2015-06-13T19:20:56Z urn:sha1:ccfb965433c67f3bda935a3cdf334be2e3c4348d Off by default, build behaves normally. WITH_META_MODE we get auto objdir creation, the ability to start build from anywhere in the tree. Still need to add real targets under targets/ to build packages. Differential Revision: D2796 Reviewed by: brooks imp 2015-06-08T23:35:17Z Simon J. Gerraty sjg@FreeBSD.org 2015-06-08T23:35:17Z urn:sha1:44d314f704764f0247a540648a4b4fc3e8012133 2015-05-27T01:19:58Z Simon J. Gerraty sjg@FreeBSD.org 2015-05-27T01:19:58Z urn:sha1:98e0ffaefb0f241cda3a72395d3be04192ae0d47 2015-04-07T16:48:23Z Takanori Watanabe takawata@FreeBSD.org 2015-04-07T16:48:23Z urn:sha1:8d6f425ddd8021ae2257ba9682f8844254ecdde1 This will fix build. 2015-04-06T09:42:23Z Gleb Smirnoff glebius@FreeBSD.org 2015-04-06T09:42:23Z urn:sha1:56d5e0967c9980b42eccf9bacd986d669fd86990 Sponsored by: Nginx, Inc. 2014-11-30T12:52:33Z Gleb Smirnoff glebius@FreeBSD.org 2014-11-30T12:52:33Z urn:sha1:0f9d0a73a495b204ea02cf1da28db1bdd0c7e40b o Introduce a notion of "not ready" mbufs in socket buffers. These mbufs are now being populated by some I/O in background and are referenced outside. This forces following implications: - An mbuf which is "not ready" can't be taken out of the buffer. - An mbuf that is behind a "not ready" in the queue neither. - If sockbet buffer is flushed, then "not ready" mbufs shouln't be freed. o In struct sockbuf the sb_cc field is split into sb_ccc and sb_acc. The sb_ccc stands for ""claimed character count", or "committed character count". And the sb_acc is "available character count". Consumers of socket buffer API shouldn't already access them directly, but use sbused() and sbavail() respectively. o Not ready mbufs are marked with M_NOTREADY, and ready but blocked ones with M_BLOCKED. o New field sb_fnrdy points to the first not ready mbuf, to avoid linear search. o New function sbready() is provided to activate certain amount of mbufs in a socket buffer. A special note on SCTP: SCTP has its own sockbufs. Unfortunately, FreeBSD stack doesn't yet allow protocol specific sockbufs. Thus, SCTP does some hacks to make itself compatible with FreeBSD: it manages sockbufs on its own, but keeps sb_cc updated to inform the stack of amount of data in them. The new notion of "not ready" data isn't supported by SCTP. Instead, only a mechanical substitute is done: s/sb_cc/sb_ccc/. A proper solution would be to take away struct sockbuf from struct socket and allow protocols to implement their own socket buffers, like SCTP already does. This was discussed with rrs@. Sponsored by: Netflix Sponsored by: Nginx, Inc.