FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.3.0 2019-01-15T06:52:34Z 2019-01-15T06:52:34Z Xin LI delphij@FreeBSD.org 2019-01-15T06:52:34Z urn:sha1:7f9e8187d45b739fdf0f9302127e46fad7a27f8e 2018-09-29T00:44:23Z Sean Eric Fagan sef@FreeBSD.org 2018-09-29T00:44:23Z urn:sha1:dc8f03b53541cf5cb6d1d1049944d68db99cf578 r336017 This exposes ZFS user and group quotas via the normal quatactl(2) mechanism. (Read-only at this point, however.) In particular, this is to allow rpc.rquotad query quotas for NFS mounts, allowing users to see their quotas on the hosts using the datasets. The changes specifically: * Add new RPC entry points for querying quotas. * Changes the library routines to allow non-UFS quotas. * Changes rquotad to check for quotas on mounted filesystems, rather than being limited to entries in /etc/fstab * Lastly, adds a VFS entry-point for ZFS to query quotas. Note that this makes one unavoidable behavioural change: if quotas are enabled, then they can be queried, as opposed to the current method of checking for quotas being specified in fstab. (With ZFS, if there are user or group quotas, they're used, always.) r338799 Author: kib Fix ZFS VFS op quotactl to follow busy protocol. Approved by: mav Sponsored by: iXsystems, inc 2018-07-11T19:48:14Z Alan Somers asomers@FreeBSD.org 2018-07-11T19:48:14Z urn:sha1:53059e9d5bfc1bb000915ae07ab72cd8a04fe95b pty.3: Add a HISTORY section These functions were first added in 4.3 BSD-Reno, according to http://unix.superglobalmegacorp.com/ and the CSRG svn repository. Reviewed by: bcr, bjk Differential Revision: https://reviews.freebsd.org/D15652 2018-07-04T18:01:53Z Ed Maste emaste@FreeBSD.org 2018-07-04T18:01:53Z urn:sha1:80d7e7fc359886de3d96a4dc13f96682f06574c8 This helps to ensure we will not lose SIGINT sent by parent to child. PR: 212562, 228492 2018-07-03T14:40:19Z Bartek Rutkowski robak@FreeBSD.org 2018-07-03T14:40:19Z urn:sha1:0da88cf198479864e48a41c021c70ff896b41107 humanize_number(3): fix math edge case in rounding large numbers Fix for remainder overflow, when in rare cases adding remainder to divider exceeded 1 and turned the total to 1000 in final formatting, taking up the space for the unit character. The fix continues the division of the original number if the above case happens -- added the appropriate check to the for loop performing the division. This lowers the value shown, to make it fit into the buffer space provided (1.0M for 4+1 character buffer, as used by ls). Add test case for the reported bug and extend test program to support providing buffer length (ls -lh uses 5, tests hard-coded 4). PR: 224498 2018-03-29T02:50:57Z Eitan Adler eadler@FreeBSD.org 2018-03-29T02:50:57Z urn:sha1:4ab2e064d7950be84256d671a7ae93f87cc6aa36 This was intended to be a non-functional change. It wasn't. The commit message was thus wrong. In addition it broke arm, and merged crypto related code. Revert with prejudice. This revert skips files touched in r316370 since that commit was since MFCed. This revert also skips files that require $FreeBSD$ property changes. Thank you to those who helped me get out of this mess including but not limited to gonzo, kevans, rgrimes. Requested by: gjb (re) 2018-03-25T01:34:44Z Sevan Janiyan sevan@FreeBSD.org 2018-03-25T01:34:44Z urn:sha1:6419b6bcbdf7d24117642bb8fa418af91a33938e Add caveat to kinfo_getvmmap(3) explaining high CPU utilisation. Based on kib's reply on https://lists.freebsd.org/pipermail/freebsd-hackers/2016-July/049710.html 2018-03-14T03:19:51Z Eitan Adler eadler@FreeBSD.org 2018-03-14T03:19:51Z urn:sha1:be5d0b9566b13fdf8cabebb63334cbec12bfc409 These changes are incomplete but are making it difficult to determine what other changes can/should be merged. No objections from: pfg 2017-11-15T12:17:51Z Baptiste Daroussin bapt@FreeBSD.org 2017-11-15T12:17:51Z urn:sha1:6f3ff0ac7a83e4d0a8cdc72a33e036ac73f193b5 Fix some nroff style issue 2017-05-09T23:31:09Z Pedro F. Giffuni pfg@FreeBSD.org 2017-05-09T23:31:09Z urn:sha1:abfc30335288c889c4e95cb5722be6d3a9275d45 lib: initial use of reallocarray(3). Make some use of reallocarray, attempting to limit it to cases where the parameters are unsigned and there is some theoretical chance of overflow.