cvs commit: src/sys/ufs/ufs ufs_inode.c

Xin LI delphij at
Fri Sep 23 20:45:31 PDT 2005

On Fri, Sep 23, 2005 at 09:04:02PM +0000, Christian S.J. Peron wrote:
> On Fri, Sep 23, 2005 at 08:49:57PM +0000, Xin LI wrote:
> [..]
> >   Log:
> >   Restore a historical ufs_inactive behavior that has been changed
> >   in rev. 1.40 of ufs_inode.c, which allows an inode being truncated
> >   even when the filesystem itself is marked RDONLY.  A subsequent
> >   call of UFS_TRUNCATE (ffs_truncate) would panic the system as it
> >   asserts that it can only be called when the filesystem is mounted
> >   read-write (same changeset, rev. 1.74 of sys/ufs/ffs/ffs_inode.c).
> >   
> Just to make sure that I am understanding you correctly here: You have
> restored a behaviour which can result in inode truncation, even on read
> only filesystems? Or you removed this behaviour?

Er...  My bad English...

I mean that "No writes to read-only file system" behavior was restored.
Rev. 1.40 allows some writes to read-only filesystem, which can cause
problem when mounting a corrupted problem.


More information about the cvs-src mailing list