From: syzbot <syzbot+76a072c2f8a60280bd70@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtSearch
Date: Tue, 28 Nov 2023 11:47:20 -0800 [thread overview]
Message-ID: <000000000000cc8fe9060b3bafa3@google.com> (raw)
In-Reply-To: <000000000000459c6205ea318e35@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtSearch
Author: dave.kleikamp@oracle.com
#syz fix: jfs: define xtree root and page independently
On 11/25/23 5:21PM, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit a779ed754e52d582b8c0e17959df063108bd0656
> Author: Dave Kleikamp <dave.kleikamp@oracle.com>
> Date: Thu Oct 5 14:16:14 2023 +0000
>
> jfs: define xtree root and page independently
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16eb55af680000
> start commit: 72a85e2b0a1e Merge tag 'spi-fix-v6.2-rc1' of git://git.ker..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
> dashboard link: https://syzkaller.appspot.com/bug?extid=76a072c2f8a60280bd70
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15802088480000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: jfs: define xtree root and page independently
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-28 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 8:50 [syzbot] UBSAN: array-index-out-of-bounds in xtSearch syzbot
2022-12-25 4:15 ` [syzbot] [jfs?] " syzbot
2023-07-16 0:39 ` syzbot
2023-11-25 23:21 ` syzbot
2023-11-28 19:47 ` syzbot [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=000000000000cc8fe9060b3bafa3@google.com \
--to=syzbot+76a072c2f8a60280bd70@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox