All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6df204b70bf3261691c5@syzkaller.appspotmail.com>
To: contact@arnaud-lcm.com, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] KASAN: out-of-bounds Read in hfsplus_bnode_move
Date: Sun, 27 Jul 2025 11:52:02 -0700	[thread overview]
Message-ID: <68867552.a00a0220.b12ec.0068.GAE@google.com> (raw)
In-Reply-To: <20250727181702.32633-1-contact@arnaud-lcm.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+6df204b70bf3261691c5@syzkaller.appspotmail.com
Tested-by: syzbot+6df204b70bf3261691c5@syzkaller.appspotmail.com

Tested on:

commit:         b711733e Merge tag 'timers-urgent-2025-07-27' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=165a98a2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=77f37fce3464f63d
dashboard link: https://syzkaller.appspot.com/bug?extid=6df204b70bf3261691c5
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch:          https://syzkaller.appspot.com/x/patch.diff?x=119298a2580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2025-07-27 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  9:48 [syzbot] [hfs?] KASAN: out-of-bounds Read in hfsplus_bnode_move syzbot
2025-07-27 18:17 ` syztest Arnaud Lecomte
2025-07-27 18:52   ` syzbot [this message]
2026-05-05 11:12 ` Forwarded: Re: [syzbot] KASAN: slab-out-of-bounds in hfs_bnode_read syzbot
     [not found] <69f9d0a1.050a0220.2ed924.c8d0@mx.google.com>
2026-05-05 16:02 ` [syzbot] [hfs?] KASAN: out-of-bounds Read in hfsplus_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=68867552.a00a0220.b12ec.0068.GAE@google.com \
    --to=syzbot+6df204b70bf3261691c5@syzkaller.appspotmail.com \
    --cc=contact@arnaud-lcm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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.