[lkml]   [2007]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 00/23] per device dirty throttling -v8
    On Sat, Aug 04, 2007 at 09:16:35PM +0200, Florian Weimer wrote:
    > * Andrew Morton:
    > > The easy preventive is to mount with data=writeback. Maybe that should
    > > have been the default.
    > The documentation I could find suggests that this may lead to a
    > security weakness (old data in blocks of a file that was grown just
    > before the crash leaks to a different user). XFS overwrites that data
    > with zeros upon reboot, which tends to irritate users when it happens.

    XFS has never overwritten data on reboot. It leaves holes when the kernel has
    failed to write out data. A hole == zeros so XFS does not expose stale data in
    this situation. As it is, the underlying XFS problem (lack of synchronisation
    between inode size update and data writes has been mostly fixed in 2.6.22 by
    only updating the file size to be written to disk on data I/O completion.

    FWIW, fsync() would prevent this from happening, but many application writers
    seem strangely reluctant to put fsync() calls into code to ensure the data
    they write is safely on disk.....


    Dave Chinner
    Principal Engineer
    SGI Australian Software Group
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-08-06 02:27    [W:0.031 / U:3.272 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site