From: Pavel Skripkin <paskripkin@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+16bcb127fb73baeecb14@syzkaller.appspotmail.com
Subject: Re: [PATCH] NFC: port100: fix use-after-free in port100_send_complete
Date: Thu, 10 Mar 2022 00:22:08 +0300 [thread overview]
Message-ID: <4078dca8-b5d7-7f84-5605-2f5a98563137@gmail.com> (raw)
In-Reply-To: <b46bfa75-2c87-61d9-c0fc-33efb2678f27@gmail.com>
On 3/9/22 21:27, Pavel Skripkin wrote:
> Hi Krzysztof,
>
> On 3/9/22 12:52, Krzysztof Kozlowski wrote:
>>
>>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>>
>> Thanks, this looks good. I think I saw similar patterns also in other
>> drivers, e.g. pn533. I will check it later, but if you have spare time,
>> feel free to investigate.
>>
>> Similar cases (unresolved):
>> https://syzkaller.appspot.com/bug?extid=1dc8b460d6d48d7ef9ca
This one is crazy :) No logs from driver at all. Even can't find where
probe failure comes from (or even is there any failures...)
>> https://syzkaller.appspot.com/bug?extid=abd2e0dafb481b621869
Looks like this patch fixes it.
>> https://syzkaller.appspot.com/bug?extid=dbec6695a6565a9c6bc0
>>
This one is already fixed. Fix bisection is bogus, but this bug is not
reproducible anymore.
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2022-03-09 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 18:50 Pavel Skripkin
2022-03-09 9:52 ` Krzysztof Kozlowski
2022-03-09 18:27 ` Pavel Skripkin
2022-03-09 21:22 ` Pavel Skripkin [this message]
2022-03-10 4:10 ` patchwork-bot+netdevbpf
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=4078dca8-b5d7-7f84-5605-2f5a98563137@gmail.com \
--to=paskripkin@gmail.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+16bcb127fb73baeecb14@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®