From: syzbot <syzbot+55a7541cfd25df68109e@syzkaller.appspotmail.com>
To: brauner@kernel.org, dave.kleikamp@oracle.com,
ghandatmanas@gmail.com, jfs-discussion@lists.sourceforge.net,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, liushixin2@huawei.com,
mirimmad17@gmail.com, mushi.shar@gmail.com, nogikh@google.com,
osmtendev@gmail.com, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtInsert
Date: Wed, 27 Dec 2023 13:35:05 -0800 [thread overview]
Message-ID: <0000000000008edf40060d8492e2@google.com> (raw)
In-Reply-To: <00000000000046566805e997132d@google.com>
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=104e23c9e80000
start commit: 830b3c68c1fb Linux 6.1
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1b610daf3807bd5c
dashboard link: https://syzkaller.appspot.com/bug?extid=55a7541cfd25df68109e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175d3e57880000
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-27 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 16:32 [syzbot] UBSAN: array-index-out-of-bounds in xtInsert syzbot
2023-12-27 21:35 ` 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=0000000000008edf40060d8492e2@google.com \
--to=syzbot+55a7541cfd25df68109e@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=dave.kleikamp@oracle.com \
--cc=ghandatmanas@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=mirimmad17@gmail.com \
--cc=mushi.shar@gmail.com \
--cc=nogikh@google.com \
--cc=osmtendev@gmail.com \
--cc=shaggy@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.