From: patchwork-bot+netdevbpf@kernel.org
To: Minsuk Kang <linuxlovemin@yonsei.ac.kr>
Cc: kuba@kernel.org, krzysztof.kozlowski@linaro.org,
netdev@vger.kernel.org, aloisio.almeida@openbossa.org,
sameo@linux.intel.com, lauro.venancio@openbossa.org,
linville@tuxdriver.com, dokyungs@yonsei.ac.kr,
jisoo.jang@yonsei.ac.kr
Subject: Re: [PATCH net v2] nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()
Date: Mon, 09 Jan 2023 07:40:16 +0000 [thread overview]
Message-ID: <167325001614.30057.15507780040740954686.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230106082344.357906-1-linuxlovemin@yonsei.ac.kr>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 6 Jan 2023 17:23:44 +0900 you wrote:
> Fix a use-after-free that occurs in hcd when in_urb sent from
> pn533_usb_send_frame() is completed earlier than out_urb. Its callback
> frees the skb data in pn533_send_async_complete() that is used as a
> transfer buffer of out_urb. Wait before sending in_urb until the
> callback of out_urb is called. To modify the callback of out_urb alone,
> separate the complete function of out_urb and ack_urb.
>
> [...]
Here is the summary with links:
- [net,v2] nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()
https://git.kernel.org/netdev/net/c/9dab880d675b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-01-09 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 8:23 [PATCH net v2] nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame() Minsuk Kang
2023-01-09 7:40 ` patchwork-bot+netdevbpf [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=167325001614.30057.15507780040740954686.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aloisio.almeida@openbossa.org \
--cc=dokyungs@yonsei.ac.kr \
--cc=jisoo.jang@yonsei.ac.kr \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=lauro.venancio@openbossa.org \
--cc=linuxlovemin@yonsei.ac.kr \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sameo@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).