In message <[EMAIL PROTECTED]>, Bruce Evans writes: >On Sun, 5 Jan 2003 [EMAIL PROTECTED] wrote: > >> I always wondered why specfs would insist on no locking, but I never >> had much ambition for finding out. > >Me too. It seems to be mostly a mistake. > >> >Fixing specfs is simple: >> >> This is not tested with DEVFS I take it ? > >It doesn't affect devfs because devfs doesn't go through ufs. It goes >straight to the default vnodeop table so it gets std* since it doesn't >override them.
Uhm, no. DEVFS only goes to the default vector for directories, for devices it goes to spec_vnoperate. >I'm getting some other panics. One while writing this was >"bwrite: buffer is not busy???". Yes, I'm hunting that one atm, but havn't found a way to reproduce. Did you get any complaints about the wrong strategy for the wrong type of node before this panic ? Do you have DEBUG_VFS_LOCKS in your kernel ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
