Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp4472667ybx; Mon, 4 Nov 2019 14:01:18 -0800 (PST) X-Google-Smtp-Source: APXvYqz+rP+6qEV/V76cErUGlIuZUO4rMwXuYtFc2ntJQFXYWa4DDruNRodYM/x1M2hmQptT/+1e X-Received: by 2002:a17:906:400f:: with SMTP id v15mr8132120ejj.126.1572904878640; Mon, 04 Nov 2019 14:01:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572904878; cv=none; d=google.com; s=arc-20160816; b=XTxDFhpblFOfNaDeJXoKtTMbumybOaKtD0VmyzXFKEg8KqA2aEwttDpNvGOufkhcVw jwUw7z1NEGfG1xl8mb4yvipo3TRWMGVrOoZ4g4PfssneAyREKbEKc63AqKaEgf64RrUk N81SrpC+ql99WeMFp0JJxEoM6At3H43hygiukL6nd99uJgLDXMa/6EtuwPDmKKc+OOX7 5eBHhxbVM2rM0Bvw25/pjNWJcqEqTVu1ogNjRx/EsZA2ULAWLdVDtDWgbJm0hY5fNKMU fxhqnpM7qoqMLPDnh0Lp+qQgUazRnooppDMOzmfsQUKyVZeWLUzejVX1YAVmsRzM+1pV k6rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=iwYf+Bp2TPzYBSsSwmivwBOfArOuj4L4iMJ6uU7WMbA=; b=eZE12IX36CicpQHkLRz28WpLkCElREpVr7aM20YsrITNDIBjXnTVroXko8/VjXRER0 Y/ODi+yMXGMj1tncSJ2KfG8ai2wri/pzTKFDKzVPlwh1oOM7t6GI1N3xqijABXPO8W3+ 1mucJNBp0g1PBtMC9uZsQKfvkT6CMZcqZOymEe2Cih3hI6DpzTxBDsIqxiMt4Zfl0I4Y R1K/0nNu3wVJoip47fnp8NCGBcJ7sWzuWa+w9CaXvghqW4aTD0kzL6TNEzB75LlKBVHD Att7P8bmROfJ6Z5SwK/56VAf0D/JrevsgOtq5cqcoDJ67t/+k8+7DgdDFF2c64dttpQa RZdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="xV/GsrQc"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v20si7996496edm.254.2019.11.04.14.00.55; Mon, 04 Nov 2019 14:01:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="xV/GsrQc"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388540AbfKDV5K (ORCPT + 99 others); Mon, 4 Nov 2019 16:57:10 -0500 Received: from mail.kernel.org ([198.145.29.99]:53088 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388530AbfKDV5H (ORCPT ); Mon, 4 Nov 2019 16:57:07 -0500 Received: from localhost (6.204-14-84.ripe.coltfrance.com [84.14.204.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 85739217F4; Mon, 4 Nov 2019 21:57:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572904627; bh=iSuchusAehub8/OSSTazSzsq4ZRiyFsHmrWUsdoSclw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=xV/GsrQcLXPNOmZUOtLOj4io+851Q6b1wQjSOSjvQ2FKKJ6yugUm5Z1CfgLZubB4u LpSEXA+zUHCbPk/YWyUvxAQlW20ipXagnpIf5NyZeDgHfJfYOSneoiXtD3pdqETEmz arPtUuQ9FAZkPzj/pHCbvEPo9AN/R89ieAqt87zY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Chao Yu , Jaegeuk Kim , Sasha Levin Subject: [PATCH 4.19 014/149] f2fs: fix to recover inode->i_flags of inode block during POR Date: Mon, 4 Nov 2019 22:43:27 +0100 Message-Id: <20191104212133.874700194@linuxfoundation.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191104212126.090054740@linuxfoundation.org> References: <20191104212126.090054740@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Chao Yu [ Upstream commit 0c093b590efb5c1ccdc835868dc2ae94bd2e14dc ] Testcase to reproduce this bug: 1. mkfs.f2fs /dev/sdd 2. mount -t f2fs /dev/sdd /mnt/f2fs 3. touch /mnt/f2fs/file 4. sync 5. chattr +a /mnt/f2fs/file 6. xfs_io -a /mnt/f2fs/file -c "fsync" 7. godown /mnt/f2fs 8. umount /mnt/f2fs 9. mount -t f2fs /dev/sdd /mnt/f2fs 10. xfs_io /mnt/f2fs/file There is no error when opening this file w/o O_APPEND, but actually, we expect the correct result should be: /mnt/f2fs/file: Operation not permitted The root cause is, in recover_inode(), we recover inode->i_flags more than F2FS_I(inode)->i_flags, so fix it. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim Signed-off-by: Sasha Levin --- fs/f2fs/recovery.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c index 281ba46b5b359..2c3be4c3c626f 100644 --- a/fs/f2fs/recovery.c +++ b/fs/f2fs/recovery.c @@ -226,6 +226,7 @@ static void recover_inode(struct inode *inode, struct page *page) F2FS_I(inode)->i_advise = raw->i_advise; F2FS_I(inode)->i_flags = le32_to_cpu(raw->i_flags); + f2fs_set_inode_flags(inode); F2FS_I(inode)->i_gc_failures[GC_FAILURE_PIN] = le16_to_cpu(raw->i_gc_failures); -- 2.20.1