From: patchwork-bot+netdevbpf@kernel.org
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: s.shtylyov@omp.ru, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] ravb: Fix use-after-free issues
Date: Fri, 06 Oct 2023 23:30:27 +0000 [thread overview]
Message-ID: <169663502753.14259.5824699296193501364.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231005011201.14368-1-yoshihiro.shimoda.uh@renesas.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Oct 2023 10:11:59 +0900 you wrote:
> This patch series fixes use-after-free issues in ravb_remove().
> The original patch is made by Zheng Wang [1]. And, I made the patch
> 1/2 which I found other issue in the ravb_remove().
>
> [1]
> https://lore.kernel.org/netdev/20230725030026.1664873-1-zyytlz.wz@163.com/
>
> [...]
Here is the summary with links:
- [net,v2,1/2] ravb: Fix up dma_free_coherent() call in ravb_remove()
https://git.kernel.org/netdev/net/c/e6864af61493
- [net,v2,2/2] ravb: Fix use-after-free issue in ravb_tx_timeout_work()
https://git.kernel.org/netdev/net/c/397144287071
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-10-06 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 1:11 [PATCH net v2 0/2] ravb: Fix use-after-free issues Yoshihiro Shimoda
2023-10-05 1:12 ` [PATCH net v2 1/2] ravb: Fix up dma_free_coherent() call in ravb_remove() Yoshihiro Shimoda
2023-10-05 1:12 ` [PATCH net v2 2/2] ravb: Fix use-after-free issue in ravb_tx_timeout_work() Yoshihiro Shimoda
2023-10-06 23:30 ` 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=169663502753.14259.5824699296193501364.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s.shtylyov@omp.ru \
--cc=yoshihiro.shimoda.uh@renesas.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