From: Viacheslav Dubeyko <vdubeyko@redhat.com>
To: Sam Sun <samsun1006219@gmail.com>,
slava@dubeyko.com, glaubitz@physik.fu-berlin.de,
frank.li@vivo.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com
Subject: Re: [BUG] hfs: crafted image can deadlock in hfs_mdb_commit()
Date: Mon, 25 May 2026 10:12:07 -0700 [thread overview]
Message-ID: <155a19235c64afa717aeb19c8d596d2b45887df3.camel@redhat.com> (raw)
In-Reply-To: <CAEkJfYMB47v1yOWHB8q2dc8kf=uj-rLO=+yMyudwPguJ8Kd3jA@mail.gmail.com>
On Sat, 2026-05-23 at 14:49 +0800, Sam Sun wrote:
> Dear developers and maintainers,
>
> We found a reproducible hung task in HFS with a crafted filesystem
> image. The C reproducer and a small proposed patch are included below.
> The crash report shows:
>
If you would like to submit the patch, then, please, prepare and send the formal
patch. Currently, this message is completely unmanageable.
Thanks,
Slava.
prev parent reply other threads:[~2026-05-25 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 6:49 Sam Sun
2026-05-25 17:12 ` Viacheslav Dubeyko [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=155a19235c64afa717aeb19c8d596d2b45887df3.camel@redhat.com \
--to=vdubeyko@redhat.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samsun1006219@gmail.com \
--cc=slava@dubeyko.com \
--cc=syzkaller@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
all inboxes | Powered by JetHome®