ext4: code clean up for dio fallocate handling
authorMingming <cmm@us.ibm.com>
Tue, 3 Nov 2009 19:44:54 +0000 (14:44 -0500)
committerTheodore Ts'o <tytso@mit.edu>
Tue, 3 Nov 2009 19:44:54 +0000 (14:44 -0500)
commit4b70df181611012a3556f017b57dfcef7e1d279f
tree95da7ccaea96227b597078c1c5f2a7571d959e99
parent5f5249507e4b5c4fc0f9c93f33d133d8c95f47e1
ext4: code clean up for dio fallocate handling

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>
fs/ext4/inode.c