Date: Fri, 23 Sep 2005 21:04:02 +0000 From: "Christian S.J. Peron" <csjp@FreeBSD.org> To: Xin LI <delphij@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ufs ufs_inode.c Message-ID: <20050923210402.GA50245@freefall.freebsd.org> In-Reply-To: <200509232049.j8NKnvIj024351@repoman.freebsd.org> References: <200509232049.j8NKnvIj024351@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? -- Christian S.J. Peron csjp@FreeBSD.ORG FreeBSD Committer FreeBSD Security Team
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050923210402.GA50245>