[lkml]   [2006]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 20/20] honor r/w changes at do_remount() time
    On Mon, Jul 03, 2006 at 10:30:14AM -0700, Dave Hansen wrote:
    > On Wed, 2006-06-28 at 06:19 +0100, Al Viro wrote:
    > > * make the moments when i_nlink hits 0 bump the superblock writers
    > > count; drop it when such sucker gets freed on final iput.
    > Could you elaborate on this one a bit?
    > I assume that there are rules that once i_nlink hits 0, it never goes
    > back up again. It seems that a whole bunch (if not all) of the
    > individual filesystems do things to it. Is it really necessary to go
    > into all of those looking for the places that i_nlink hits 0? Seems
    > like it would be an awful lot of patching.

    Not that much... That happens in three methods (->unlink(), ->rename(),
    ->rmdir()) and yes, we really want to track those. Think for a minute
    and you'll see why - we don't want to allow remount ro when there is
    a pending truncate/freeing inode.
    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: 2006-07-03 19:50    [W:0.022 / U:0.480 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site