From: David Maximiliano Hermitte <davemadmaxxx@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>,
Jori Koolstra <jkoolstra@xs4all.nl>
Cc: djwong@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+97e301b4b82ae803d21b@syzkaller.appspotmail.com,
David Maximiliano Hermitte <davemadmaxxx@gmail.com>
Subject: Re: [PATCH v2] hfs: return -EFSCORRUPTED instead of BUG() in hfs_write_inode()
Date: Thu, 11 Jun 2026 17:57:53 +0000 [thread overview]
Message-ID: <20260611175753.1410325-1-davemadmaxxx@gmail.com> (raw)
Hello Slava, Jori, all,
I wanted to share one additional diagnostic result from our side.
We are not HFS maintainers, and I do not want to present this as a final patch proposal. We used a small change only as a route-checking experiment, to verify whether the crash ending in hfs_write_inode() / BUG() can be prevented by rejecting corrupt metadata earlier.
The experimental change was in fs/hfs/btree.c, after reading the HFS B-tree header:
if (tree->root >= tree->node_count)
goto fail_folio;
if (tree->leaf_head >= tree->node_count)
goto fail_folio;
if (tree->leaf_tail >= tree->node_count)
goto fail_folio;
if (tree->leaf_count && (!tree->leaf_head || !tree->leaf_tail))
goto fail_folio;
if (tree->depth > tree->node_count)
goto fail_folio;
We specifically did not modify:
fs/hfs/inode.c
hfs_write_inode()
BUG()
With the same syzbot-style reproducer and the same QEMU setup, we observed:
BEFORE / unpatched:
boot_linux_seen=true
root_mounted_seen=true
repro_started=true
VQBIT_HFS_INODE_BUG_SITE_3 line=474 hit
kernel_bug_seen=true
verdict=BEFORE_BUG_REPRODUCED
AFTER / diagnostic btree validation:
boot_linux_seen=true
root_mounted_seen=true
repro_started=true
kernel_bug_seen=false
hfs_write_inode_seen=false
kasan_seen=false
oops_seen=false
verdict=REPRO_RAN_NO_KERNEL_BUG_SEEN
So our current interpretation is:
The BUG in hfs_write_inode() appears to be the crash sink.
The corrupt state seems to be accepted earlier.
Rejecting inconsistent HFS B-tree header fields before traversal prevents the reproducer from reaching hfs_write_inode::BUG().
Again, this is not intended as a polished HFS fix. It is only evidence from a diagnostic route check. I would appreciate your opinion on whether this direction makes sense, and whether the proper fix should live around HFS B-tree / catalog metadata validation rather than changing the final BUG() in hfs_write_inode().
Best regards,
David
next reply other threads:[~2026-06-11 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 17:57 David Maximiliano Hermitte [this message]
2026-06-12 4:08 ` Viacheslav Dubeyko
-- strict thread matches above, loose matches on Subject: below --
2026-06-07 3:53 David Maximiliano Hermitte
2026-06-07 21:34 ` Jori Koolstra
2026-06-08 4:24 ` David Maximiliano Hermitte
2026-06-09 21:45 ` Viacheslav Dubeyko
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=20260611175753.1410325-1-davemadmaxxx@gmail.com \
--to=davemadmaxxx@gmail.com \
--cc=djwong@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=syzbot+97e301b4b82ae803d21b@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®