src/sys/fs/devfs/devfs_rule.c, branch releng/15.0 FreeBSD source tree devfs(5): Fix a typo in a source code comment 2024-01-20T16:25:45+00:00 Gordon Bergling gbe@FreeBSD.org 2024-01-20T16:25:45+00:00 7cf293536ebacc92150be12e0be928500e670610 - s/interpeted/interpreted/ MFC after: 3 days 
- s/interpeted/interpreted/

MFC after:	3 days
sys: Remove $FreeBSD$: two-line .h pattern 2023-08-16T17:54:11+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:54:11+00:00 95ee2897e98f5d444f26ed2334cc7c439f9c16c6 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ 
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD 2023-05-12T16:44:03+00:00 Warner Losh imp@FreeBSD.org 2023-05-10T15:40:58+00:00 4d846d260e2b9a3d4d0a701462568268cbfe7a5b 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 
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
sys/fs: further adoption of SPDX licensing ID tags. 2017-11-27T15:15:37+00:00 Pedro F. Giffuni pfg@FreeBSD.org 2017-11-27T15:15:37+00:00 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. 
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.
make path matching in devfs rules consistent and sane (and safer) 2013-07-26T14:25:58+00:00 Andriy Gapon avg@FreeBSD.org 2013-07-26T14:25:58+00:00 8e94193e58657c5b88b9d0e9049b2db7b5664e1e Before this change path matching had the following features: - for device nodes the patterns were matched against full path - in the above case '/' in a path could be matched by a wildcard - for directories and links only the last component was matched So, for example, a pattern like 're*' could match the following entries: - re0 device - responder/u0 device - zvol/recpool directory Although it was possible to work around this behavior (once it was spotted and understood), it was very confusing and contrary to documentation. Now we always match a full path for all types of devfs entries (devices, directories, links) and a '/' has to be matched explicitly. This behavior follows the shell globbing rules. This change is originally developed by Jaakko Heinonen. Many thanks! PR: kern/122838 Submitted by: jh MFC after: 4 weeks 
Before this change path matching had the following features:
- for device nodes the patterns were matched against full path
- in the above case '/' in a path could be matched by a wildcard
- for directories and links only the last component was matched

So, for example, a pattern like 're*' could match the following entries:
- re0 device
- responder/u0 device
- zvol/recpool directory

Although it was possible to work around this behavior (once it was spotted
and understood), it was very confusing and contrary to documentation.

Now we always match a full path for all types of devfs entries (devices,
directories, links) and a '/' has to be matched explicitly.
This behavior follows the shell globbing rules.

This change is originally developed by Jaakko Heinonen.
Many thanks!

PR:		kern/122838
Submitted by:	jh
MFC after:	4 weeks
Introduce the "ruleset=number" option for devfs(5) mounts. 2012-02-09T10:09:12+00:00 Martin Matuska mm@FreeBSD.org 2012-02-09T10:09:12+00:00 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 
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
- fix duplicate "a a" in some comments 2011-11-13T17:06:33+00:00 Eitan Adler eadler@FreeBSD.org 2011-11-13T17:06:33+00:00 3b6dc18ef553ab572cca0be3ce55e0132f35b0fb Submitted by: eadler Approved by: simon MFC after: 3 days 
Submitted by:	eadler
Approved by:	simon
MFC after:	3 days
- Assert that dm_lock is exclusively held in devfs_rules_apply() and 2010-12-15T16:42:44+00:00 Jaakko Heinonen jh@FreeBSD.org 2010-12-15T16:42:44+00:00 ef456eec9533e1777fad9e48a34c6f4877e8da96 in devfs_vmkdir() while adding the entry to de_list of the parent. - Apply devfs rules to newly created directories and symbolic links. PR: kern/125034 Submitted by: Mateusz Guzik (original version) 
  in devfs_vmkdir() while adding the entry to de_list of the parent.
- Apply devfs rules to newly created directories and symbolic links.

PR:		kern/125034
Submitted by:	Mateusz Guzik (original version)
Handle the special ruleset 0 in devfs_ruleset_use(). An attempt set the 2010-12-12T08:52:13+00:00 Jaakko Heinonen jh@FreeBSD.org 2010-12-12T08:52:13+00:00 2f66e90fc7408b8dd0d7eb726a9ae9f079175816 current ruleset to 0 with command "devfs ruleset 0" triggered a KASSERT in devfs_ruleset_create(). PR: kern/125030 Submitted by: Mateusz Guzik 
current ruleset to 0 with command "devfs ruleset 0" triggered a KASSERT
in devfs_ruleset_create().

PR:		kern/125030
Submitted by:	Mateusz Guzik
Add new make_dev_p(9) flag MAKEDEV_ETERNAL to inform devfs that created 2010-08-06T09:42:15+00:00 Konstantin Belousov kib@FreeBSD.org 2010-08-06T09:42:15+00:00 3979450b4cca0a16d6e71b5856e7642c28ddd063 cdev will never be destroyed. Propagate the flag to devfs vnodes as VV_ETERNVALDEV. Use the flags to avoid acquiring devmtx and taking a thread reference on such nodes. In collaboration with: pho MFC after: 1 month 
cdev will never be destroyed. Propagate the flag to devfs vnodes as
VV_ETERNVALDEV. Use the flags to avoid acquiring devmtx and taking a
thread reference on such nodes.

In collaboration with:	pho
MFC after:	1 month