From: patchwork-bot+netdevbpf@kernel.org
To: Ziyang Xuan <william.xuanziyang@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: macvlan: fix potential UAF problem for lowerdev
Date: Mon, 14 Mar 2022 10:10:11 +0000 [thread overview]
Message-ID: <164725261157.13129.12736326177131205389.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1646989143.git.william.xuanziyang@huawei.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 11 Mar 2022 17:02:41 +0800 you wrote:
> Add the reference operation to lowerdev of macvlan to avoid
> the potential UAF problem under the following known scenario:
>
> Someone module puts the NETDEV_UNREGISTER event handler to a
> work, and lowerdev is accessed in the work handler. But when
> the work is excuted, lowerdev has been destroyed because upper
> macvlan did not get reference to lowerdev correctly.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: macvlan: fix potential UAF problem for lowerdev
https://git.kernel.org/netdev/net-next/c/291ac68478d9
- [net-next,2/2] net: macvlan: add net device refcount tracker
https://git.kernel.org/netdev/net-next/c/1f4a5983d623
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:[~2022-03-14 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 9:02 Ziyang Xuan
2022-03-11 9:03 ` [PATCH net-next 1/2] " Ziyang Xuan
2022-03-11 9:04 ` [PATCH net-next 2/2] net: macvlan: add net device refcount tracker Ziyang Xuan
2022-03-14 10:10 ` 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=164725261157.13129.12736326177131205389.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=william.xuanziyang@huawei.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®