From: syzbot <syzbot+a19ca73b21fe8bc69101@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] WARNING in hfs_bnode_create
Date: Fri, 17 Apr 2026 09:21:41 -0700 [thread overview]
Message-ID: <69e25e15.a00a0220.1bd0ca.000d.GAE@google.com> (raw)
In-Reply-To: <001a11c1461c14bf9e0568fd0cd6@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] WARNING in hfs_bnode_create
Author: tristmd@gmail.com
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>From 89ec6a61f81d25f4bf256b4747be2dec6a36627a Mon Sep 17 00:00:00 2001
From: Tristan Madani <tristan@talencesecurity.com>
Date: Fri, 17 Apr 2026 16:15:20 +0000
Subject: [PATCH] hfs: return error when bnode already hashed in
hfs_bnode_create()
hfs_bnode_create() uses WARN_ON(1) and returns the existing node
when a bnode is already hashed. On corrupted filesystems this
triggers repeated kernel WARNINGs. Replace with ERR_PTR(-EIO)
to properly signal the error to callers.
Reported-by: syzbot+a19ca73b21fe8bc69101@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=a19ca73b21fe8bc69101
Signed-off-by: Tristan Madani <tristan@talencesecurity.com>
---
fs/hfs/bnode.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/hfs/bnode.c b/fs/hfs/bnode.c
index 13d58c5..255db8e 100644
--- a/fs/hfs/bnode.c
+++ b/fs/hfs/bnode.c
@@ -517,8 +517,7 @@ struct hfs_bnode *hfs_bnode_create(struct hfs_btree *tree, u32 num)
spin_unlock(&tree->hash_lock);
if (node) {
pr_crit("new node %u already hashed?\n", num);
- WARN_ON(1);
- return node;
+ return ERR_PTR(-EIO);
}
node = __hfs_bnode_create(tree, num);
if (!node)
--
2.47.3
prev parent reply other threads:[~2026-04-17 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 3:02 WARNING in hfs_bnode_create syzbot
2026-04-17 10:12 ` Forwarded: [PATCH] hfs: return error when bnode already hashed in syzbot
2026-04-17 16:21 ` syzbot [this message]
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=69e25e15.a00a0220.1bd0ca.000d.GAE@google.com \
--to=syzbot+a19ca73b21fe8bc69101@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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