From: Hrutvik Kanabar <hrkanabar@gmail.com> To: Hrutvik Kanabar <hrutvik@google.com> Cc: Marco Elver <elver@google.com>, Aleksandr Nogikh <nogikh@google.com>, kasan-dev@googlegroups.com, Alexander Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger.kernel@dilger.ca>, linux-ext4@vger.kernel.org, Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>, David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>, linux-f2fs-devel@lists.sourceforge.net, "Darrick J . Wong" <djwong@kernel.org>, linux-xfs@vger.kernel.org, Namjae Jeon <linkinjeon@kernel.org>, Sungjong Seo <sj1557.seo@samsung.com>, Anton Altaparmakov <anton@tuxera.com>, linux-ntfs-dev@lists.sourceforge.net Subject: [PATCH RFC 4/7] fs/exfat: support `DISABLE_FS_CSUM_VERIFICATION` config option Date: Fri, 14 Oct 2022 08:48:34 +0000 [thread overview] Message-ID: <20221014084837.1787196-5-hrkanabar@gmail.com> (raw) In-Reply-To: <20221014084837.1787196-1-hrkanabar@gmail.com> From: Hrutvik Kanabar <hrutvik@google.com> When `DISABLE_FS_CSUM_VERIFICATION` is enabled, bypass checksum verification. Signed-off-by: Hrutvik Kanabar <hrutvik@google.com> --- fs/exfat/nls.c | 3 ++- fs/exfat/super.c | 3 +++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/fs/exfat/nls.c b/fs/exfat/nls.c index 705710f93e2d..f0f92eaf6ccc 100644 --- a/fs/exfat/nls.c +++ b/fs/exfat/nls.c @@ -696,7 +696,8 @@ static int exfat_load_upcase_table(struct super_block *sb, brelse(bh); } - if (index >= 0xFFFF && utbl_checksum == chksum) + if (IS_ENABLED(CONFIG_DISABLE_FS_CSUM_VERIFICATION) || + (index >= 0xFFFF && utbl_checksum == chksum)) return 0; exfat_err(sb, "failed to load upcase table (idx : 0x%08x, chksum : 0x%08x, utbl_chksum : 0x%08x)", diff --git a/fs/exfat/super.c b/fs/exfat/super.c index 35f0305cd493..7418858792b3 100644 --- a/fs/exfat/super.c +++ b/fs/exfat/super.c @@ -564,6 +564,9 @@ static int exfat_verify_boot_region(struct super_block *sb) if (!bh) return -EIO; + if (IS_ENABLED(CONFIG_DISABLE_FS_CSUM_VERIFICATION)) + return 0; + for (i = 0; i < sb->s_blocksize; i += sizeof(u32)) { p_chksum = (__le32 *)&bh->b_data[i]; if (le32_to_cpu(*p_chksum) != chksum) { -- 2.38.0.413.g74048e4d9e-goog
WARNING: multiple messages have this Message-ID (diff)
From: Hrutvik Kanabar <hrkanabar@gmail.com> To: Hrutvik Kanabar <hrutvik@google.com> Cc: "Darrick J . Wong" <djwong@kernel.org>, Chris Mason <clm@fb.com>, Andreas Dilger <adilger.kernel@dilger.ca>, kasan-dev@googlegroups.com, linux-ext4@vger.kernel.org, Namjae Jeon <linkinjeon@kernel.org>, Marco Elver <elver@google.com>, Josef Bacik <josef@toxicpanda.com>, Alexander Viro <viro@zeniv.linux.org.uk>, David Sterba <dsterba@suse.com>, Jaegeuk Kim <jaegeuk@kernel.org>, Anton Altaparmakov <anton@tuxera.com>, Theodore Ts'o <tytso@mit.edu>, linux-ntfs-dev@lists.sourceforge.net, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-xfs@vger.kernel.org, Aleksandr Nogikh <nogikh@google.com>, linux-fsdevel@vger.kernel.org, Sungjong Seo <sj1557.seo@samsung.com>, linux-btrfs@vger.kernel.org Subject: [f2fs-dev] [PATCH RFC 4/7] fs/exfat: support `DISABLE_FS_CSUM_VERIFICATION` config option Date: Fri, 14 Oct 2022 08:48:34 +0000 [thread overview] Message-ID: <20221014084837.1787196-5-hrkanabar@gmail.com> (raw) In-Reply-To: <20221014084837.1787196-1-hrkanabar@gmail.com> From: Hrutvik Kanabar <hrutvik@google.com> When `DISABLE_FS_CSUM_VERIFICATION` is enabled, bypass checksum verification. Signed-off-by: Hrutvik Kanabar <hrutvik@google.com> --- fs/exfat/nls.c | 3 ++- fs/exfat/super.c | 3 +++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/fs/exfat/nls.c b/fs/exfat/nls.c index 705710f93e2d..f0f92eaf6ccc 100644 --- a/fs/exfat/nls.c +++ b/fs/exfat/nls.c @@ -696,7 +696,8 @@ static int exfat_load_upcase_table(struct super_block *sb, brelse(bh); } - if (index >= 0xFFFF && utbl_checksum == chksum) + if (IS_ENABLED(CONFIG_DISABLE_FS_CSUM_VERIFICATION) || + (index >= 0xFFFF && utbl_checksum == chksum)) return 0; exfat_err(sb, "failed to load upcase table (idx : 0x%08x, chksum : 0x%08x, utbl_chksum : 0x%08x)", diff --git a/fs/exfat/super.c b/fs/exfat/super.c index 35f0305cd493..7418858792b3 100644 --- a/fs/exfat/super.c +++ b/fs/exfat/super.c @@ -564,6 +564,9 @@ static int exfat_verify_boot_region(struct super_block *sb) if (!bh) return -EIO; + if (IS_ENABLED(CONFIG_DISABLE_FS_CSUM_VERIFICATION)) + return 0; + for (i = 0; i < sb->s_blocksize; i += sizeof(u32)) { p_chksum = (__le32 *)&bh->b_data[i]; if (le32_to_cpu(*p_chksum) != chksum) { -- 2.38.0.413.g74048e4d9e-goog _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-10-14 8:50 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-14 8:48 [PATCH RFC 0/7] fs: Debug config option to disable filesystem checksum verification for fuzzing Hrutvik Kanabar 2022-10-14 8:48 ` [f2fs-dev] " Hrutvik Kanabar 2022-10-14 8:48 ` [PATCH RFC 1/7] fs: create `DISABLE_FS_CSUM_VERIFICATION` config option Hrutvik Kanabar 2022-10-14 8:48 ` [f2fs-dev] " Hrutvik Kanabar 2022-10-14 8:48 ` [PATCH RFC 2/7] fs/ext4: support " Hrutvik Kanabar 2022-10-14 8:48 ` [f2fs-dev] " Hrutvik Kanabar 2022-10-14 8:48 ` [PATCH RFC 3/7] fs/btrfs: " Hrutvik Kanabar 2022-10-14 8:48 ` [f2fs-dev] " Hrutvik Kanabar 2022-10-14 10:23 ` Qu Wenruo 2022-10-14 10:23 ` [f2fs-dev] " Qu Wenruo via Linux-f2fs-devel 2022-10-17 8:43 ` Dmitry Vyukov 2022-10-17 8:43 ` [f2fs-dev] " Dmitry Vyukov via Linux-f2fs-devel 2022-10-17 9:35 ` Qu Wenruo 2022-10-17 9:35 ` [f2fs-dev] " Qu Wenruo 2022-10-14 8:48 ` Hrutvik Kanabar [this message] 2022-10-14 8:48 ` [f2fs-dev] [PATCH RFC 4/7] fs/exfat: " Hrutvik Kanabar 2022-10-14 8:48 ` [PATCH RFC 5/7] fs/xfs: " Hrutvik Kanabar 2022-10-14 8:48 ` [f2fs-dev] " Hrutvik Kanabar 2022-10-14 15:44 ` Darrick J. Wong 2022-10-14 15:44 ` [f2fs-dev] " Darrick J. Wong 2022-10-17 8:32 ` Dmitry Vyukov 2022-10-17 8:32 ` [f2fs-dev] " Dmitry Vyukov via Linux-f2fs-devel 2022-10-14 8:48 ` [PATCH RFC 6/7] fs/ntfs: " Hrutvik Kanabar 2022-10-14 8:48 ` [f2fs-dev] " Hrutvik Kanabar 2022-10-14 8:48 ` [f2fs-dev] [PATCH RFC 7/7] fs/f2fs: " Hrutvik Kanabar 2022-10-14 8:48 ` Hrutvik Kanabar 2022-10-14 9:15 ` [PATCH RFC 0/7] fs: Debug config option to disable filesystem checksum verification for fuzzing David Sterba 2022-10-14 9:15 ` [f2fs-dev] " David Sterba 2022-10-17 8:31 ` Dmitry Vyukov 2022-10-17 8:31 ` [f2fs-dev] " Dmitry Vyukov via Linux-f2fs-devel 2022-10-17 12:02 ` David Sterba 2022-10-17 12:02 ` [f2fs-dev] " David Sterba
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20221014084837.1787196-5-hrkanabar@gmail.com \ --to=hrkanabar@gmail.com \ --cc=adilger.kernel@dilger.ca \ --cc=anton@tuxera.com \ --cc=chao@kernel.org \ --cc=clm@fb.com \ --cc=djwong@kernel.org \ --cc=dsterba@suse.com \ --cc=elver@google.com \ --cc=hrutvik@google.com \ --cc=jaegeuk@kernel.org \ --cc=josef@toxicpanda.com \ --cc=kasan-dev@googlegroups.com \ --cc=linkinjeon@kernel.org \ --cc=linux-btrfs@vger.kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-ntfs-dev@lists.sourceforge.net \ --cc=linux-xfs@vger.kernel.org \ --cc=nogikh@google.com \ --cc=sj1557.seo@samsung.com \ --cc=tytso@mit.edu \ --cc=viro@zeniv.linux.org.uk \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.