From: syzbot <syzbot+5867885efe39089b339b@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com, davem@davemloft.net,
dvyukov@google.com, jiri@nvidia.com, kuba@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, vishal.moola@gmail.com,
willy@infradead.org
Subject: Re: [syzbot] [ntfs3?] UBSAN: array-index-out-of-bounds in truncate_inode_pages_range
Date: Wed, 02 Aug 2023 08:24:27 -0700 [thread overview]
Message-ID: <00000000000066e89c0601f24249@google.com> (raw)
In-Reply-To: <000000000000117c7505e7927cb4@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=129893bea80000
start commit: e8bc52cb8df8 Merge tag 'driver-core-6.1-rc1' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7579993da6496f03
dashboard link: https://syzkaller.appspot.com/bug?extid=5867885efe39089b339b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=153137b8880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=123cae34880000
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
parent reply other threads:[~2023-08-02 15:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000117c7505e7927cb4@google.com>]
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=00000000000066e89c0601f24249@google.com \
--to=syzbot+5867885efe39089b339b@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vishal.moola@gmail.com \
--cc=willy@infradead.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).