From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:42485 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964787AbcI0Qnx (ORCPT ); Tue, 27 Sep 2016 12:43:53 -0400 From: Jan Kara To: linux-fsdevel@vger.kernel.org Cc: linux-nvdimm@lists.01.org, Dan Williams , Ross Zwisler , Jan Kara Subject: [PATCH 3/6] ext4: Remove clearing of BH_New bit for zeroed blocks Date: Tue, 27 Sep 2016 18:43:32 +0200 Message-Id: <1474994615-29553-4-git-send-email-jack@suse.cz> In-Reply-To: <1474994615-29553-1-git-send-email-jack@suse.cz> References: <1474994615-29553-1-git-send-email-jack@suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: So far we did not return BH_New buffers from ext4_dax_get_block() because that would trigger racy zeroing in DAX code. This zeroing is gone these days so we can remove the workaround. Signed-off-by: Jan Kara --- fs/ext4/inode.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c index 87150122d361..7ccd6fd7819d 100644 --- a/fs/ext4/inode.c +++ b/fs/ext4/inode.c @@ -3298,11 +3298,6 @@ int ext4_dax_get_block(struct inode *inode, sector_t iblock, if (ret < 0) return ret; } - /* - * At least for now we have to clear BH_New so that DAX code - * doesn't attempt to zero blocks again in a racy way. - */ - clear_buffer_new(bh_result); return 0; } #else -- 2.6.6