From patchwork Wed Jan 2 17:45:42 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [3/5] ext4: Remove bogus wait for unwritten extents in ext4_ind_direct_IO Date: Wed, 02 Jan 2013 07:45:42 -0000 From: Jan Kara X-Patchwork-Id: 209123 Message-Id: <1357148744-4895-4-git-send-email-jack@suse.cz> To: Ted Tso Cc: linux-ext4@vger.kernel.org, Jan Kara When using indirect blocks there is no possibility to have any unwritten extents. So wait for them in ext4_ind_direct_IO() is just bogus. Signed-off-by: Jan Kara Reviewed-by: Zheng Liu --- fs/ext4/indirect.c | 5 ----- 1 files changed, 0 insertions(+), 5 deletions(-) diff --git a/fs/ext4/indirect.c b/fs/ext4/indirect.c index 20862f9..993247c 100644 --- a/fs/ext4/indirect.c +++ b/fs/ext4/indirect.c @@ -807,11 +807,6 @@ ssize_t ext4_ind_direct_IO(int rw, struct kiocb *iocb, retry: if (rw == READ && ext4_should_dioread_nolock(inode)) { - if (unlikely(atomic_read(&EXT4_I(inode)->i_unwritten))) { - mutex_lock(&inode->i_mutex); - ext4_flush_unwritten_io(inode); - mutex_unlock(&inode->i_mutex); - } /* * Nolock dioread optimization may be dynamically disabled * via ext4_inode_block_unlocked_dio(). Check inode's state