kern/60687: devfs(8) on newly mounted devfs doesn't work
Colin Percival
cperciva at daemonology.net
Mon Dec 29 05:20:12 PST 2003
>Number: 60687
>Category: kern
>Synopsis: devfs(8) on newly mounted devfs doesn't work
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Dec 29 05:20:07 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Colin Percival
>Release: FreeBSD 5.2-RC2 i386
>Organization:
>Environment:
System: FreeBSD fafnir.daemonology.net 5.2-RC2 FreeBSD 5.2-RC2 #0: Mon Dec 22 07:23:48 GMT 2003 root at wv1u.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
>Description:
If devfs(8) is run to modify a newly mounted devfs, the rules may
not be applied properly.
>How-To-Repeat:
# mount -t devfs devfs /tmp/dev
# devfs -m /tmp/dev rule apply hide
# ls /tmp/dev | wc
87 87 524
# umount /tmp/dev
>Fix:
If the devfs is examined before devfs(8) is called, the expected behaviour
is seen:
# mount -t devfs devfs /tmp/dev
# ls /tmp/dev > /dev/null
# devfs -m /tmp/dev rule apply hide
# ls /tmp/dev | wc
0 0 0
# umount /tmp/dev
I can only guess that devfs entries are being created on-demand, and that
attempting to apply devfs rules isn't prompting the creation of all the
entries.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list