From: syzbot <syzbot+c19afa60d78984711078@syzkaller.appspotmail.com>
To: davem@davemloft.net, hdanton@sina.com, jiri@nvidia.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl
Date: Mon, 17 Jul 2023 13:22:24 -0700 [thread overview]
Message-ID: <00000000000077b5650600b48ed0@google.com> (raw)
In-Reply-To: <00000000000049baa505e65e3939@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=136a0414a80000
start commit: 84368d882b96 Merge tag 'soc-fixes-6.1-3' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=24d192d47d02d9e1
dashboard link: https://syzkaller.appspot.com/bug?extid=c19afa60d78984711078
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=168fc765880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1376e745880000
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 parent reply other threads:[~2023-07-17 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000049baa505e65e3939@google.com>
2023-07-17 20:22 ` syzbot [this message]
2023-07-18 19:45 ` [syzbot] [bluetooth?] general protection fault in hci_uart_tty_ioctl Jakub Kicinski
2023-07-19 8:45 ` 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=00000000000077b5650600b48ed0@google.com \
--to=syzbot+c19afa60d78984711078@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=jiri@nvidia.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).