From: syzbot <syzbot+0558d19c373e44da3c18@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 txCommit
Date: Mon, 04 Dec 2023 06:55:13 -0800 [thread overview]
Message-ID: <0000000000002b2ead060bb04eb5@google.com> (raw)
In-Reply-To: <000000000000f841fb05eb364ce6@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 txCommit
Author: dave.kleikamp@oracle.com
#syz fix: jfs: define xtree root and page independently
On 12/2/23 11:25PM, 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=14f67ce2e80000
> start commit: d88520ad73b7 Merge tag 'pull-nfsd-fix' of git://git.kernel..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=9ee601744db6e780
> dashboard link: https://syzkaller.appspot.com/bug?extid=0558d19c373e44da3c18
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e974ed680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b2588b680000
>
> 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-12-04 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 7:55 [syzbot] UBSAN: array-index-out-of-bounds in txCommit syzbot
2022-11-26 17:09 ` syzbot
2023-12-03 5:25 ` [syzbot] [jfs?] " syzbot
2023-12-04 14:55 ` 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=0000000000002b2ead060bb04eb5@google.com \
--to=syzbot+0558d19c373e44da3c18@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 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.