From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+fa88eb476e42878f2844@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [fs?] KASAN: use-after-free Read in hpfs_get_ea
Date: Tue, 14 Oct 2025 20:12:04 +0900 [thread overview]
Message-ID: <8a2fc775-e4f7-406d-b6dd-8b1f3cd851a3@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <68794b99.a70a0220.693ce.0052.GAE@google.com>
#syz test
diff --git a/fs/hpfs/Kconfig b/fs/hpfs/Kconfig
index ac1e9318e65a..d3dfbe76be8a 100644
--- a/fs/hpfs/Kconfig
+++ b/fs/hpfs/Kconfig
@@ -15,3 +15,14 @@ config HPFS_FS
To compile this file system support as a module, choose M here: the
module will be called hpfs. If unsure, say N.
+
+config HPFS_FS_ALLOW_NO_ERROR_CHECK_MODE
+ bool "Allow no-error-check mode for maximum speed"
+ depends on HPFS_FS
+ default n
+ help
+ This option enables check=none mount option. If check=none is
+ specified, users can expect maximum speed at the cost of minimum
+ robustness. Sane users should not specify check=none option, for e.g.
+ use-after-free bug will happen when the filesystem is corrupted or
+ crafted.
diff --git a/fs/hpfs/super.c b/fs/hpfs/super.c
index 42b779b4d87f..558093b2beab 100644
--- a/fs/hpfs/super.c
+++ b/fs/hpfs/super.c
@@ -285,7 +285,9 @@ static const struct constant_table hpfs_param_case[] = {
};
static const struct constant_table hpfs_param_check[] = {
+#ifdef CONFIG_HPFS_FS_ALLOW_NO_ERROR_CHECK_MODE
{"none", 0},
+#endif
{"normal", 1},
{"strict", 2},
{}
next prev parent reply other threads:[~2025-10-14 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 19:14 syzbot
2025-07-18 12:32 ` Forwarded: Private message regarding: " syzbot
2025-07-18 12:57 ` syzbot
2025-07-19 0:58 ` syzbot
2025-07-19 7:57 ` Forwarded: syzbot
2025-07-20 6:54 ` Forwarded: syzbot
2025-07-20 7:29 ` Forwarded: syzbot
2025-10-14 11:12 ` Tetsuo Handa [this message]
2025-10-14 12:23 ` [syzbot] [fs?] KASAN: use-after-free Read in hpfs_get_ea syzbot
2025-10-14 13:30 ` [PATCH] hpfs: make check=none mount option excludable Tetsuo Handa
2025-10-14 18:25 ` Mikulas Patocka
[not found] <df725c07-3ee4-477d-b4d6-21fb4afc61a8n@googlegroups.com>
2025-07-18 12:40 ` [syzbot] [fs?] KASAN: use-after-free Read in hpfs_get_ea syzbot
[not found] <62d528e9-2414-4e50-8e3f-c4cac3526858n@googlegroups.com>
2025-07-18 13:27 ` syzbot
[not found] <8b62af1c-64f0-4742-a96b-34d23635c089n@googlegroups.com>
2025-07-19 1:19 ` syzbot
[not found] <CAMp3bLVwzu1F+BAYf=UbNXqDq-8H6NjtxUXe+ChNO9_bu7tN8g@mail.gmail.com>
2025-07-19 8:21 ` syzbot
[not found] <CAMp3bLXKFqL5nkRkTVBNOKv968bK61yAT=b1wkoz+SZqtk0yiQ@mail.gmail.com>
2025-07-20 7:12 ` syzbot
[not found] <CAMp3bLWE1Q17He7mzu8S-VTe9Sackn8YryD6L0msjyPpifmyBg@mail.gmail.com>
2025-07-20 7:49 ` syzbot
2025-07-20 12:34 [PATCH] hpfs: add checks for ea addresses Antoni Pokusinski
2025-07-20 13:49 ` [syzbot] [fs?] KASAN: use-after-free Read in hpfs_get_ea syzbot
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=8a2fc775-e4f7-406d-b6dd-8b1f3cd851a3@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+fa88eb476e42878f2844@syzkaller.appspotmail.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®