FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=stable%2F7 2016-02-02T19:29:29Z 2016-02-02T19:29:29Z John Baldwin jhb@FreeBSD.org 2016-02-02T19:29:29Z urn:sha1:546d648266fdaaa364294be44359fd13ff6f9f7f namecache hit. This was ommitted due to a merging error in r238913. The effect was to usually break caching of negative name lookups in the NFS client. Submitted by: bde 2012-12-14T08:54:52Z Baptiste Daroussin bapt@FreeBSD.org 2012-12-14T08:54:52Z urn:sha1:dc86b17ab81c2a8ae135517e59b12dff8cc3baed return ERANGE if the buffer is too small to contain the login as documented in the manpage Reviewed by: cognet, kib 2012-11-15T18:05:38Z Baptiste Daroussin bapt@FreeBSD.org 2012-11-15T18:05:38Z urn:sha1:45af412bbaf5a13cc6b4d53d4e58483adb4b605a small style fix 2012-10-29T03:52:19Z Eitan Adler eadler@FreeBSD.org 2012-10-29T03:52:19Z urn:sha1:b0d6456689b59b06e99539d92fdda86ac05190c6 Update the kill(2) and killpg(2) man pages to the modern permission checks. Also indicate killpg(2) is POSIX compliant. Correct the killpg(2) return values: Return EPERM if processes were found but they were unable to be signaled. Return the first error from p_cansignal if no signal was successful. Discussed with: jilles Approved by: cperciva (implicit) 2012-07-30T19:05:41Z John Baldwin jhb@FreeBSD.org 2012-07-30T19:05:41Z urn:sha1:2e89c94eaa744b214d8f3a7180c3825152dfafe2 - For dotdot lookup in nfs_lookup, inline the vn_vget_ino() to prevent operating on the unmounted mount point and freed mount data in case of forced unmount performed while dvp is unlocked to nget the target vnode. - Close a race in NFS lookup processing that could result in stale name cache entries on one client when a directory was renamed on another client. The root cause for the stale entry being trusted is that each per-vnode nfsnode structure has a single 'n_ctime' timestamp used to validate positive name cache entries. However, if there are multiple entries for a single vnode, they all share a single timestamp. To fix this, extend the name cache to allow filesystems to optionally store a timestamp value in each name cache entry. The NFS clients now fetch the timestamp associated with each name cache entry and use that to validate cache hits instead of the timestamps previously stored in the nfsnode. Another part of the fix is that the NFS clients now use timestamps from the post-op attributes of RPCs when adding name cache entries rather than pulling the timestamps out of the file's attribute cache. The latter is subject to races with other lookups updating the attribute cache concurrently. - Adjust the nfs_skip_wcc_data_onerr setting so that it does not block post-op attributes for ENOENT errors now that the name caching logic depends on working post-op attributes. Tested by: Mark Saad nonesuch longcount org 2012-01-21T07:57:27Z Alan Cox alc@FreeBSD.org 2012-01-21T07:57:27Z urn:sha1:08f1f9aeb916d250b9c60e65a1d08619bf5b48e4 Fix the handling of an empty kmem map by sysctl_kmem_map_free(). Eliminate the possibility of 32-bit arithmetic overflow in the calculation of vm_kmem_size that may occur if the system administrator has specified a vm.vm_kmem_size tunable value that exceeds the hard cap. Eliminate stale numbers from a comment. PR: 162741 2012-01-15T20:52:01Z Eitan Adler eadler@FreeBSD.org 2012-01-15T20:52:01Z urn:sha1:b436217e2169953ab29f3c3eec3048d54327c621 - Fix ktrace leakage if error is set PR: kern/163098 Approved by: sbruno 2012-01-09T03:03:43Z Eitan Adler eadler@FreeBSD.org 2012-01-09T03:03:43Z urn:sha1:783c6507e934fcc9163ba84f071e42539685bfde - Fix typos s/(more|less) then|\1 than/ Approved by: brucec 2011-10-14T22:52:46Z Xin LI delphij@FreeBSD.org 2011-10-14T22:52:46Z urn:sha1:195d4553548c3441527bfdf4c6c71dc54992e61b Return proper errno when we hit error when doing sanity check. This fixes dtrace crashes when module is not compiled with CTF data. Submitted by: Paul Ambrose ambrosehua at gmail.com 2011-10-11T14:05:39Z Konstantin Belousov kib@FreeBSD.org 2011-10-11T14:05:39Z urn:sha1:8d851ea3f28c2cce0a434292682d315ce50bd629 Move parts of the commit log for r166167, where Tor explained the interaction between vnode locks and vfs_busy(), into comment. Comment is slightly edited to better fit into RELENG_7 reality.