On Sun, 13 Feb 2005, Christoph Hellwig wrote:
> > > + vfs_check_frozen(inode->i_sb, SB_FREEZE_WRITE);
> >
> > hm, I didn't pay much attention to this stuff. Shouldn't the direct-io
> > code be waiting as well? Are all paths which can write to the bdev supposed
> > to be blocked? kjournald?
>
> This should block new data writers. New metadata writes need to be
> blocked in the individual filesystem, and only when the state is set
> to SB_FREEZE_TRANS (a few steps later in freeze_bdev).
Why this distinction? At least on NTFS metadata is stored in normal files
(everything is a file in NTFS) and the same readpage/writepage address
space operations are used to access both...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
