From: patchwork-bot+netdevbpf@kernel.org
To: Zheng Wang <zyytlz.wz@163.com>
Cc: timur@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, hackerzheng666@gmail.com,
1395428693sheep@gmail.com, alex000young@gmail.com
Subject: Re: [PATCH net v2] net: qcom/emac: Fix use after free bug in emac_remove due to race condition
Date: Mon, 20 Mar 2023 09:20:17 +0000 [thread overview]
Message-ID: <167930401750.16850.14731742864962914143.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230318080526.785457-1-zyytlz.wz@163.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 18 Mar 2023 16:05:26 +0800 you wrote:
> In emac_probe, &adpt->work_thread is bound with
> emac_work_thread. Then it will be started by timeout
> handler emac_tx_timeout or a IRQ handler emac_isr.
>
> If we remove the driver which will call emac_remove
> to make cleanup, there may be a unfinished work.
>
> [...]
Here is the summary with links:
- [net,v2] net: qcom/emac: Fix use after free bug in emac_remove due to race condition
https://git.kernel.org/netdev/net/c/6b6bc5b8bd2d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-20 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 8:05 [PATCH net v2] net: qcom/emac: Fix use after free bug in emac_remove due to race condition Zheng Wang
2023-03-20 9:20 ` patchwork-bot+netdevbpf [this message]
2023-03-20 19:22 ` Jakub Kicinski
2023-03-23 3:49 ` Zheng Hacker
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=167930401750.16850.14731742864962914143.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=1395428693sheep@gmail.com \
--cc=alex000young@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hackerzheng666@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=timur@kernel.org \
--cc=zyytlz.wz@163.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).