FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F13.2.0 2020-08-11T14:27:57Z 2020-08-11T14:27:57Z Mateusz Guzik mjg@FreeBSD.org 2020-08-11T14:27:57Z urn:sha1:3b44443626603f65bba2804f08a7dfa6e6675bb4 This removes a lot of special casing from the VFS layer. Reviewed by: kib (previous version) Tested by: pho (previous version) Differential Revision: https://reviews.freebsd.org/D25612 2020-08-10T11:46:39Z Mateusz Guzik mjg@FreeBSD.org 2020-08-10T11:46:39Z urn:sha1:ca423b858bf4800bb22963e8133b72499bb18d24 Fixes buildworld after r364069 2020-08-10T10:36:43Z Mateusz Guzik mjg@FreeBSD.org 2020-08-10T10:36:43Z urn:sha1:7b19bddac8f6ae5a356ffbca80f087d3654b8363 Tested by: pho 2017-11-27T15:15:37Z Pedro F. Giffuni pfg@FreeBSD.org 2017-11-27T15:15:37Z urn:sha1:d63027b668c055c83bad6191a9986616380c86e4 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. 2012-02-09T10:09:12Z Martin Matuska mm@FreeBSD.org 2012-02-09T10:09:12Z urn:sha1:17d84d611f995d5d33602ff8aed1ae6d2a3ea92c Add support for updating the devfs mount (currently only changing the ruleset number is supported). Check mnt_optnew with vfs_filteropt(9). This new option sets the specified ruleset number as the active ruleset of the new devfs mount and applies all its rules at mount time. If the specified ruleset doesn't exist, a new empty ruleset is created. MFC after: 1 month 2010-10-12T15:58:52Z Jaakko Heinonen jh@FreeBSD.org 2010-10-12T15:58:52Z urn:sha1:27877c99031f3d14427c7da72086bb156f9632a5 Discussed with: kib, phk 2010-09-27T17:47:09Z Jaakko Heinonen jh@FreeBSD.org 2010-09-27T17:47:09Z urn:sha1:d318c565d74496343ec299b3ace0ae9eb744dba1 links. The reference counting is needed to be able to determine if a specific devfs path exists. For true device file paths we can traverse the cdevp_list but a separate directory list is needed for user created symbolic links. Add a new directory entry flag DE_USER to mark entries which should unreference their parent directory on deletion. A new function to traverse cdevp_list and the directory list will be introduced in a separate commit. Idea from: kib Reviewed by: kib 2010-09-21T16:49:02Z Jaakko Heinonen jh@FreeBSD.org 2010-09-21T16:49:02Z urn:sha1:6adc52306ad41aacb0f80da53955e922601c7140 code: - Accept devfs_mount and devfs_dirent as the arguments instead of a vnode. This generalizes the function so that it can be used from contexts where vnode references are not available. - Accept NULL cnp argument. No '/' will be appended, if a NULL cnp is provided. - Make the function global and add its prototype to devfs.h. Reviewed by: kib 2010-09-15T14:23:55Z Jaakko Heinonen jh@FreeBSD.org 2010-09-15T14:23:55Z urn:sha1:89d10571dbd835a79c96ba9a6de5b8607c234295 devfs_delete() now recursively removes empty parent directories unless the DEVFS_DEL_NORECURSE flag is specified. devfs_delete() can't be called anymore with a parent directory vnode lock held because the possible parent directory deletion needs to lock the vnode. Thus we unlock the parent directory vnode in devfs_remove() before calling devfs_delete(). Call devfs_populate_vp() from devfs_symlink() and devfs_vptocnp() as now directories can get removed. Add a check for DE_DOOMED flag to devfs_populate_vp() because devfs_delete() drops dm_lock before the VI_DOOMED vnode flag gets set. This ensures that devfs_populate_vp() returns an error for directories which are in progress of deletion. Reviewed by: kib Discussed on: freebsd-current (mostly silence) 2010-08-12T15:29:07Z Jaakko Heinonen jh@FreeBSD.org 2010-08-12T15:29:07Z urn:sha1:64040d3978f50ee74cf1ef61e4ecdc6ab12d824a if the device file appears during or after the link creation. User created symbolic links are now inserted at the head of the directory entry list after the "." and ".." entries. A new directory entry flag DE_COVERED indicates that an entry is covered by a symbolic link. PR: kern/114057 Reviewed by: kib Idea from: kib Discussed on: freebsd-current (mostly silence)