From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "penguin-kernel@I-love.SAKURA.ne.jp"
<penguin-kernel@I-love.SAKURA.ne.jp>,
"slava@dubeyko.com" <slava@dubeyko.com>
Cc: "shardul.b@mpiricsoftware.com" <shardul.b@mpiricsoftware.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jkoolstra@xs4all.nl" <jkoolstra@xs4all.nl>,
"mehdi.benhadjkhelifa@gmail.com" <mehdi.benhadjkhelifa@gmail.com>
Subject: RE: [GIT PULL] hfs/hfsplus changes for 7.0-rc1
Date: Tue, 10 Feb 2026 18:11:35 +0000 [thread overview]
Message-ID: <30889d31f1cda6371139533d71d1ea688b2d5b79.camel@ibm.com> (raw)
In-Reply-To: <6a99ecc3-ba7c-4687-9252-b4ea91ce9dfa@I-love.SAKURA.ne.jp>
On Tue, 2026-02-10 at 20:12 +0900, Tetsuo Handa wrote:
> On 2026/02/07 9:26, Viacheslav Dubeyko wrote:
> > Jori Koolstra has fixed the syzbot reported issue of triggering
> > BUG_ON() in the case of corrupted superblock. This patch replaces
> > the BUG_ON() in multiple places with proper error handling and
> > resolves the syzbot reported bug.
>
> I think that commit b226804532a8 ("hfs: Replace BUG_ON with error handling for CNID count checks") is incomplete.
>
> Since atomic64_t is signed 64bits and U32_MAX is unsigned 32bits, the comparison
> "if (atomic64_read(&sbi->next_id) > U32_MAX)" becomes false when sbi->next_id >= ((-1ULL) / 2) + 1.
> I guess that a corrupted filesystem can have e.g. sbi->next_id == -1, and
> "if (atomic64_read(&sbi->next_id) >> 32)" would check that the upper 32bits are all 0.
>
>
>
> Also, I confirmed that this pull request did not include a fix for
> https://urldefense.proofpoint.com/v2/url?u=https-3A__syzkaller.appspot.com_bug-3Fid-3Dee595bf9e099fff0610828e37bbbcdb7a2933f58&d=DwICaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=q5bIm4AXMzc8NJu1_RGmnQ2fMWKq4Y4RAkElvUgSs00&m=oSYPrjvqOFJcM1QikgNde5oUhIdGdMpum5UQMLayiJS0yQrJtT-rfZXJJ6rqaBd_&s=ztXY-L3aBc2mxTwLuNk3drfU-ca8BOnIOSLbfUesA-o&e= .
> I'm waiting for next version of patch for this problem.
>
If something was missed in the patch, then you or Jori are welcome to send the
fix.
Thanks,
Slava.
prev parent reply other threads:[~2026-02-10 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 0:26 Viacheslav Dubeyko
2026-02-07 1:18 ` Tetsuo Handa
2026-02-07 8:55 ` John Paul Adrian Glaubitz
2026-02-07 9:44 ` Tetsuo Handa
2026-02-10 0:50 ` pr-tracker-bot
2026-02-10 11:12 ` Tetsuo Handa
2026-02-10 18:11 ` 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=30889d31f1cda6371139533d71d1ea688b2d5b79.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jkoolstra@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mehdi.benhadjkhelifa@gmail.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=shardul.b@mpiricsoftware.com \
--cc=slava@dubeyko.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®