From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6EE0C35280 for ; Fri, 1 Apr 2022 15:40:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1356570AbiDAPhk (ORCPT ); Fri, 1 Apr 2022 11:37:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55932 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1350518AbiDAPAH (ORCPT ); Fri, 1 Apr 2022 11:00:07 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 880F65AEFC; Fri, 1 Apr 2022 07:47:29 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 1422960AC0; Fri, 1 Apr 2022 14:47:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1E1F3C2BBE4; Fri, 1 Apr 2022 14:47:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648824448; bh=Zbxh8TkrFsVLjYcz4lCCEieGwYLeyDTCFvG176JUxg0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=p6LjYdZIpXT9ZmFBiY4cIjtsIJMbjEMw8kNdI2JWhzPyyTviY2JTfRPws3MaEilPp MNGqrpY7RKi2ej3yCrloDWVSj+e3xvsfmqRC0mv12j+II5ygy3DR7ni0eC9VdJWR+9 Vp1vHyJXJMTMBA20r93IIvLKXjtLC2V6JtiWy/b9rNT7woSWCpyOXaVohFH+Lla30p w49X6l69cQpjTV+/lfj48yLvKODwoKWU/nE43mzGIF0BaLCGRAsQz+2kH1Ntv1bBma nNE9FifvGnXKjY9/KismFdbJJWXMU9qurgduU+Q9/VnCxeSkGj1aflL6/zA8wn3LOi K7ESvyveOTseA== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Qinghua Jin , Colin Ian King , Jan Kara , Christian Brauner , Andrew Morton , Linus Torvalds , Sasha Levin , willy@infradead.org, damien.lemoal@opensource.wdc.com, songmuchun@bytedance.com Subject: [PATCH AUTOSEL 4.19 29/29] minix: fix bug when opening a file with O_DIRECT Date: Fri, 1 Apr 2022 10:46:12 -0400 Message-Id: <20220401144612.1955177-29-sashal@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220401144612.1955177-1-sashal@kernel.org> References: <20220401144612.1955177-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Qinghua Jin [ Upstream commit 9ce3c0d26c42d279b6c378a03cd6a61d828f19ca ] Testcase: 1. create a minix file system and mount it 2. open a file on the file system with O_RDWR|O_CREAT|O_TRUNC|O_DIRECT 3. open fails with -EINVAL but leaves an empty file behind. All other open() failures don't leave the failed open files behind. It is hard to check the direct_IO op before creating the inode. Just as ext4 and btrfs do, this patch will resolve the issue by allowing to create the file with O_DIRECT but returning error when writing the file. Link: https://lkml.kernel.org/r/20220107133626.413379-1-qhjin.dev@gmail.com Signed-off-by: Qinghua Jin Reported-by: Colin Ian King Reviewed-by: Jan Kara Acked-by: Christian Brauner Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds Signed-off-by: Sasha Levin --- fs/minix/inode.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/minix/inode.c b/fs/minix/inode.c index 03fe8bac36cf..3ce91ad1ee1b 100644 --- a/fs/minix/inode.c +++ b/fs/minix/inode.c @@ -450,7 +450,8 @@ static const struct address_space_operations minix_aops = { .writepage = minix_writepage, .write_begin = minix_write_begin, .write_end = generic_write_end, - .bmap = minix_bmap + .bmap = minix_bmap, + .direct_IO = noop_direct_IO }; static const struct inode_operations minix_symlink_inode_operations = { -- 2.34.1