From: Namjae Jeon <linkinjeon@kernel.org>
To: syzbot <syzbot+5216036fc59c43d1ee02@syzkaller.appspotmail.com>
Cc: brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [exfat?] WARNING in __rt_mutex_slowlock_locked (2)
Date: Fri, 7 Nov 2025 16:29:46 +0900 [thread overview]
Message-ID: <CAKYAXd8HxiEGLS4zBFEKAcxT_qtAFM8Ng0YKZ5seTnB3A_-RVQ@mail.gmail.com> (raw)
In-Reply-To: <690d2bd5.a70a0220.22f260.000f.GAE@google.com>
[-- Attachment #1: Type: text/plain, Size: 10 bytes --]
#syz test
[-- Attachment #2: 0001-exfat-return-error-if-start_clu-is-invalid.patch --]
[-- Type: text/x-patch, Size: 954 bytes --]
From 25892e8de955d717859f02e8da65c109156c4ee1 Mon Sep 17 00:00:00 2001
From: Namjae Jeon <linkinjeon@kernel.org>
Date: Fri, 7 Nov 2025 16:27:10 +0900
Subject: [PATCH] exfat: return error if ->start_clu is invalid
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
---
fs/exfat/namei.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/exfat/namei.c b/fs/exfat/namei.c
index 745dce29ddb5..4dd09da1aa92 100644
--- a/fs/exfat/namei.c
+++ b/fs/exfat/namei.c
@@ -657,10 +657,9 @@ static int exfat_find(struct inode *dir, const struct qstr *qname,
info->start_clu = le32_to_cpu(ep2->dentry.stream.start_clu);
if (!is_valid_cluster(sbi, info->start_clu) && info->size) {
- exfat_warn(sb, "start_clu is invalid cluster(0x%x)",
+ exfat_fs_error(sb, "start_clu is invalid cluster(0x%x)",
info->start_clu);
- info->size = 0;
- info->valid_size = 0;
+ return -EIO;
}
if (info->valid_size > info->size) {
--
2.25.1
next prev parent reply other threads:[~2025-11-07 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 23:14 [syzbot] [exfat?] WARNING in __rt_mutex_slowlock_locked (2) syzbot
2025-11-07 7:29 ` Namjae Jeon [this message]
2025-11-07 8:29 ` syzbot
2025-11-07 9:11 ` syzbot
2025-11-08 11:06 ` Namjae Jeon
2025-11-08 11:46 ` syzbot
2025-11-12 3:37 ` Namjae Jeon
2025-11-12 4:07 ` 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=CAKYAXd8HxiEGLS4zBFEKAcxT_qtAFM8Ng0YKZ5seTnB3A_-RVQ@mail.gmail.com \
--to=linkinjeon@kernel.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzbot+5216036fc59c43d1ee02@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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: 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;
as well as URLs for NNTP newsgroup(s).