From: Aneesh Kumar K.V Date: Tue, 2 Jun 2009 12:09:35 +0000 (-0400) Subject: ext4: Clear the unwritten buffer_head flag after the extent is initialized X-Git-Tag: v2.6.27.25~2 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ef3740934e85572dce2e20cecea3341fd43647e0;p=pandora-kernel.git ext4: Clear the unwritten buffer_head flag after the extent is initialized (cherry picked from commit 2a8964d63d50dd2d65d71d342bc7fb6ef4117614) The BH_Unwritten flag indicates that the buffer is allocated on disk but has not been written; that is, the disk was part of a persistent preallocation area. That flag should only be set when a get_blocks() function is looking up a inode's logical to physical block mapping. When ext4_get_blocks_wrap() is called with create=1, the uninitialized extent is converted into an initialized one, so the BH_Unwritten flag is no longer appropriate. Hence, we need to make sure the BH_Unwritten is not left set, since the combination of BH_Mapped and BH_Unwritten is not allowed; among other things, it will result ext4's get_block() to be called over and over again during the write_begin phase of write(2). Signed-off-by: Aneesh Kumar K.V Signed-off-by: "Theodore Ts'o" Signed-off-by: Greg Kroah-Hartman --- Reading git-diff-tree failed