src/sys/fs/devfs/devfs_rule.c, branch upstream/11.1.0 FreeBSD source tree 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
Get pointer to devfs_ruleset struct after garbage collection has been 2008-06-22T14:34:38+00:00 Oleksandr Tymoshenko gonzo@FreeBSD.org 2008-06-22T14:34:38+00:00 2da528a74fd17355573de1365c381dd3bbff7573 performed. Otherwise if ruleset is used by given mountpoint and is empty it's freed by devfs_ruleset_reap and pointer becomes bogus. Submitted by: Mateusz Guzik <mjguzik@gmail.com> PR: kern/124853 
performed. Otherwise if ruleset is used by given mountpoint and is empty
it's freed by devfs_ruleset_reap and pointer becomes bogus.

Submitted by:   Mateusz Guzik <mjguzik@gmail.com>
PR:             kern/124853
Do not dereference cdev->si_cdevsw, use the dev_refthread() to properly 2008-03-20T16:08:42+00:00 Konstantin Belousov kib@FreeBSD.org 2008-03-20T16:08:42+00:00 91a35e787094b1aca363bfd0ec8380d9a38ada53 obtain the reference. In particular, this fixes the panic reported in the PR. Remove the comments stating that this needs to be done. PR: kern/119422 MFC after: 1 week 
obtain the reference. In particular, this fixes the panic reported in
the PR. Remove the comments stating that this needs to be done.

PR:	kern/119422
MFC after:	1 week
Sweep kernel replacing suser(9) calls with priv(9) calls, assigning 2006-11-06T13:42:10+00:00 Robert Watson rwatson@FreeBSD.org 2006-11-06T13:42:10+00:00 acd3428b7d3e94cef0e1881c868cb4b131d4ff41 specific privilege names to a broad range of privileges. These may require some future tweaking. Sponsored by: nCircle Network Security, Inc. Obtained from: TrustedBSD Project Discussed on: arch@ Reviewed (at least in part) by: mlaier, jmg, pjd, bde, ceri, Alex Lyashkov <umka at sevcity dot net>, Skip Ford <skip dot ford at verizon dot net>, Antoine Brodin <antoine dot brodin at laposte dot net> 
specific privilege names to a broad range of privileges.  These may
require some future tweaking.

Sponsored by:           nCircle Network Security, Inc.
Obtained from:          TrustedBSD Project
Discussed on:           arch@
Reviewed (at least in part) by: mlaier, jmg, pjd, bde, ceri,
                        Alex Lyashkov <umka at sevcity dot net>,
                        Skip Ford <skip dot ford at verizon dot net>,
                        Antoine Brodin <antoine dot brodin at laposte dot net>
Remove the NDEVFSINO and NDEVFSOVERFLOW options which no longer exists in 2006-07-17T09:07:02+00:00 Poul-Henning Kamp phk@FreeBSD.org 2006-07-17T09:07:02+00:00 9c499ad92f03f9ffbbe9d2e437f3186371ca9416 DEVFS. Remove the opt_devfs.h file now that it is empty. 
DEVFS.

Remove the opt_devfs.h file now that it is empty.