From: syzbot <syzbot+d2cdeba65d32ed1d2c4d@syzkaller.appspotmail.com>
To: chandan.babu@oracle.com, davem@davemloft.net, djwong@kernel.org,
hdanton@sina.com, jiri@nvidia.com, kuba@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] KASAN: stack-out-of-bounds Read in xfs_buf_delwri_submit_buffers
Date: Tue, 12 Sep 2023 09:09:39 -0700 [thread overview]
Message-ID: <00000000000088fbf106052bab18@google.com> (raw)
In-Reply-To: <00000000000019e05005ef9c1481@google.com>
syzbot suspects this issue was fixed by commit:
commit d772781964415c63759572b917e21c4f7ec08d9f
Author: Jakub Kicinski <kuba@kernel.org>
Date: Fri Jan 6 06:33:54 2023 +0000
devlink: bump the instance index directly when iterating
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15554ba4680000
start commit: 3ecc37918c80 Merge tag 'media/v6.1-4' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d58e7fe7f9cf5e24
dashboard link: https://syzkaller.appspot.com/bug?extid=d2cdeba65d32ed1d2c4d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170a950b880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1625948f880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: devlink: bump the instance index directly when iterating
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-12 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 7:01 [syzbot] KASAN: stack-out-of-bounds Read in xfs_buf_delwri_submit_buffers syzbot
2023-09-12 16:09 ` syzbot [this message]
2023-09-12 16:35 ` [syzbot] [xfs?] " Aleksandr Nogikh
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=00000000000088fbf106052bab18@google.com \
--to=syzbot+d2cdeba65d32ed1d2c4d@syzkaller.appspotmail.com \
--cc=chandan.babu@oracle.com \
--cc=davem@davemloft.net \
--cc=djwong@kernel.org \
--cc=hdanton@sina.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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.