From: syzbot <syzbot+2b131f51bb4af224ab40@syzkaller.appspotmail.com>
To: James.Bottomley@HansenPartnership.com, airlied@gmail.com,
daniel@ffwll.ch, davem@davemloft.net, deller@gmx.de,
deller@kernel.org, dianders@chromium.org,
dri-devel@lists.freedesktop.org, eadavis@qq.com,
edumazet@google.com, gregkh@linuxfoundation.org,
hdanton@sina.com, jernej.skrabec@gmail.com, krzk@kernel.org,
krzysztof.kozlowski@linaro.org, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-sunxi@lists.linux.dev, mripard@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
penguin-kernel@i-love.sakura.ne.jp, samuel@sholland.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, u.kleine-koenig@pengutronix.de,
wens@csie.org
Subject: Re: [syzbot] [net?] [nfc?] INFO: task hung in nfc_targets_found
Date: Mon, 24 Jun 2024 10:54:02 -0700 [thread overview]
Message-ID: <0000000000006cb461061ba67748@google.com> (raw)
In-Reply-To: <00000000000026100c060e143e5a@google.com>
syzbot suspects this issue was fixed by commit:
commit 487fa28fa8b60417642ac58e8beda6e2509d18f9
Author: Helge Deller <deller@kernel.org>
Date: Sat Apr 27 17:43:51 2024 +0000
parisc: Define sigset_t in parisc uapi header
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17038a61980000
start commit: acc657692aed keys, dns: Fix size check of V1 server-list h..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=5c882ebde8a5f3b4
dashboard link: https://syzkaller.appspot.com/bug?extid=2b131f51bb4af224ab40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103698bde80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1617e0fbe80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: parisc: Define sigset_t in parisc uapi header
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-06-24 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 0:59 [syzbot] [net?] [nfc?] INFO: task hung in nfc_targets_found syzbot
2024-01-04 5:05 ` Hillf Danton
2024-01-04 10:34 ` Tetsuo Handa
2024-01-11 19:08 ` syzbot
2024-01-14 8:20 ` [PATCH] nfc/nci: fix " Edward Adam Davis
2024-01-15 9:36 ` Krzysztof Kozlowski
2024-01-15 11:08 ` Tetsuo Handa
2024-01-15 11:15 ` Krzysztof Kozlowski
2024-01-13 17:29 ` [syzbot] [net?] [nfc?] INFO: " syzbot
2024-06-24 17:54 ` syzbot [this message]
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=0000000000006cb461061ba67748@google.com \
--to=syzbot+2b131f51bb4af224ab40@syzkaller.appspotmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=deller@kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eadavis@qq.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=samuel@sholland.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wens@csie.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 NNTP newsgroup(s).