• L
    Write back inode data pages even when the inode itself is locked · 4b89eed9
    Linus Torvalds 提交于
    In __writeback_single_inode(), when we find a locked inode and we're not
    doing a data-integrity sync, we used to just skip writing entirely,
    since we didn't want to wait for the inode to unlock.
    
    However, there's really no reason to skip writing the data pages, which
    are likely to be the the bulk of the dirty state anyway (and the main
    reason why writeback was started for the non-data-integrity case, of
    course!)
    Acked-by: NNick Piggin <nickpiggin@yahoo.com.au>
    Cc: Andrew Morton <akpm@osdl.org>,
    Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: Hugh Dickins <hugh@veritas.com>
    Cc: David Howells <dhowells@redhat.com>
    Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
    4b89eed9
fs-writeback.c 20.0 KB