/dev permissions after reboot (and panic)

Matthew Dillon dillon at apollo.backplane.com
Sat Jul 16 20:48:22 PDT 2005

:Yeah, I've tried a bunch of sync's before the reboot.  I've even seen this
:happen hours after a MAKEDEV.
:That was with no patches...just straight-up HEAD.  I'm compiling up a
:new kernel with the SOCKBUF_DEBUG patchset right now, and I'll see if
:that warning goes away.  I'll also try turning off softupdates and see
:what happens.

    I lost the 'w' permissions on my /dev/null once about two months ago 
    after rebooting my workstation (a single cpu machine), after an 

    My best guess was that it was a buffer flushing problem but it couldn't
    be if it can occur hours after the operation, so maybe its an inode
    update flag issue.  pure inode updates (i.e. just changing the 
    permissions on a file) are implemented by setting a flag in the 
    in-memory inode structure rather then by dirtying a buffer.  Those are
    supposed to be flushed every 30 seconds and of course on unmount, I will
    check the vnode/inode termination paths to make sure such inodes are
    properly flushed.

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Bugs mailing list