From: syzbot <syzbot+f1f36887d202cea1446d@syzkaller.appspotmail.com>
To: bongsu.jeon@samsung.com, davem@davemloft.net, dvyukov@google.com,
edumazet@google.com, hdanton@sina.com,
krzysztof.kozlowski@linaro.org, kuba@kernel.org,
linma@zju.edu.cn, linux-kernel@vger.kernel.org,
linux-nfc@lists.01.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nfc?] possible deadlock in nci_start_poll
Date: Sat, 25 Mar 2023 17:46:23 -0700 [thread overview]
Message-ID: <000000000000a5727605f7c2f407@google.com> (raw)
In-Reply-To: <000000000000e8fd1f05ed75bf20@google.com>
syzbot suspects this issue was fixed by commit:
commit b2e44aac91b25abbed57d785089c4b7af926a7bd
Author: Dmitry Vyukov <dvyukov@google.com>
Date: Tue Nov 15 10:00:17 2022 +0000
NFC: nci: Allow to create multiple virtual nci devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=117e50c1c80000
start commit: 0b1dcc2cf55a Merge tag 'mm-hotfixes-stable-2022-11-24' of ..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=436ee340148d5197
dashboard link: https://syzkaller.appspot.com/bug?extid=f1f36887d202cea1446d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=125fa5c5880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12508d3d880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: NFC: nci: Allow to create multiple virtual nci devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-03-26 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 22:27 [syzbot] possible deadlock in nci_start_poll syzbot
2023-03-26 0:46 ` syzbot [this message]
2023-04-11 7:06 ` [syzbot] [nfc?] " Dmitry Vyukov
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=000000000000a5727605f7c2f407@google.com \
--to=syzbot+f1f36887d202cea1446d@syzkaller.appspotmail.com \
--cc=bongsu.jeon@samsung.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linma@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).