All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+41ba9c82bce8d7101765@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: Re: [syzbot] [hfs?] KASAN: out-of-bounds Read in hfs_bnode_move
Date: Wed, 23 Jul 2025 18:52:58 -0700	[thread overview]
Message-ID: <688191fa.a00a0220.2f88df.0008.GAE@google.com> (raw)
In-Reply-To: <68811963.050a0220.248954.0005.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: Re: [syzbot] [hfs?] KASAN: out-of-bounds Read in hfs_bnode_move
Author: lizhi.xu@windriver.com

#syz test

diff --git a/fs/hfs/bnode.c b/fs/hfs/bnode.c
index cb823a8a6ba9..58c5cc7adf70 100644
--- a/fs/hfs/bnode.c
+++ b/fs/hfs/bnode.c
@@ -134,7 +134,7 @@ void hfs_bnode_move(struct hfs_bnode *node, int dst, int src, int len)
 	void *ptr;
 
 	hfs_dbg(BNODE_MOD, "movebytes: %u,%u,%u\n", dst, src, len);
-	if (!len)
+	if (len <= 0)
 		return;
 	src += node->page_offset;
 	dst += node->page_offset;

  parent reply	other threads:[~2025-07-24  1:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 17:18 [syzbot] [hfs?] KASAN: out-of-bounds Read in hfs_bnode_move syzbot
2025-07-23 17:26 ` Viacheslav Dubeyko
2025-07-24  1:52 ` syzbot [this message]
2025-07-24  9:40 ` Edward Adam Davis
2025-07-24 10:17   ` syzbot
2025-07-24 11:46 ` Edward Adam Davis
2025-07-24 15:06   ` syzbot
2025-07-24 15:08 ` [PATCH] hfs: Prevent the use of bnodes without entries Edward Adam Davis
2025-07-24 20:06   ` Viacheslav Dubeyko
2025-08-27  9:54 ` [syzbot] [hfs?] KASAN: out-of-bounds Read in hfs_bnode_move syzbot
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22  9:48 [syzbot] [hfs?] KASAN: out-of-bounds Read in hfsplus_bnode_move syzbot
2026-04-30 22:41 ` Forwarded: Re: [syzbot] [hfs?] KASAN: out-of-bounds Read in hfs_bnode_move 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=688191fa.a00a0220.2f88df.0008.GAE@google.com \
    --to=syzbot+41ba9c82bce8d7101765@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.