From: syzbot <syzbot+8040d16d30c215f821de@syzkaller.appspotmail.com>
To: bongsu.jeon@samsung.com, clement.perrochaud@nxp.com,
davem@davemloft.net, dvyukov@google.com, hdanton@sina.com,
krzysztof.kozlowski@linaro.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, michael.thalmeier@hale.at,
netdev@vger.kernel.org, r.baldyga@samsung.com,
robert.dolca@intel.com, sameo@linux.intel.com,
shikha.singh@st.com, syzkaller-bugs@googlegroups.com,
thierry.escande@linux.intel.com
Subject: Re: [syzbot] possible deadlock in virtual_nci_close
Date: Tue, 15 Nov 2022 21:58:17 -0800 [thread overview]
Message-ID: <000000000000b63a2805ed90289d@google.com> (raw)
In-Reply-To: <000000000000cceef005ed659943@google.com>
syzbot has bisected this issue to:
commit e624e6c3e777fb3dfed036b9da4d433aee3608a5
Author: Bongsu Jeon <bongsu.jeon@samsung.com>
Date: Wed Jan 27 13:08:28 2021 +0000
nfc: Add a virtual nci device driver
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1093fb59880000
start commit: 094226ad94f4 Linux 6.1-rc5
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1293fb59880000
console output: https://syzkaller.appspot.com/x/log.txt?x=1493fb59880000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d516a992a8757b5
dashboard link: https://syzkaller.appspot.com/bug?extid=8040d16d30c215f821de
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1360e2f1880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a95659880000
Reported-by: syzbot+8040d16d30c215f821de@syzkaller.appspotmail.com
Fixes: e624e6c3e777 ("nfc: Add a virtual nci device driver")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-11-16 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 3:11 [syzbot] possible deadlock in virtual_nci_close syzbot
2022-11-14 9:48 ` Dmitry Vyukov
2022-11-14 14:55 ` syzbot
2022-11-16 5:58 ` syzbot [this message]
2022-11-22 13:08 ` 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=000000000000b63a2805ed90289d@google.com \
--to=syzbot+8040d16d30c215f821de@syzkaller.appspotmail.com \
--cc=bongsu.jeon@samsung.com \
--cc=clement.perrochaud@nxp.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=hdanton@sina.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thalmeier@hale.at \
--cc=netdev@vger.kernel.org \
--cc=r.baldyga@samsung.com \
--cc=robert.dolca@intel.com \
--cc=sameo@linux.intel.com \
--cc=shikha.singh@st.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=thierry.escande@linux.intel.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).