ext4: code clean up for dio fallocate handling
commit2bcfe650d1b5c9994ce58a25efd5a6f5eb4ad0ee
authorMingming <cmm@us.ibm.com>
Tue, 3 Nov 2009 19:44:54 +0000 (3 14:44 -0500)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 14 Dec 2009 16:07:19 +0000 (14 08:07 -0800)
tree87365a4720c6ef0292054e33dccea62e669e6b1a
parent3e6c8d3881736079664aad465e26486d1d4152b9
ext4: code clean up for dio fallocate handling

(cherry picked from commit 4b70df181611012a3556f017b57dfcef7e1d279f)

The ext4_debug() call in ext4_end_io_dio() should be moved after the
check to make sure that io_end is non-NULL.

The comment above ext4_get_block_dio_write() ("Maximum number of
blocks...") is a duplicate; the original and correct comment is above
the #define DIO_MAX_BLOCKS up above.

Based on review comments from Curt Wohlgemuth.

Signed-off-by: Mingming Cao <cmm@us.ibm.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
fs/ext4/inode.c