From: patchwork-bot+netdevbpf@kernel.org
To: Congyu Liu <liu3101@purdue.edu>
Cc: davem@davemloft.net, kuba@kernel.org, yajun.deng@linux.dev,
edumazet@google.com, willemb@google.com, mkl@pengutronix.de,
rsanger@wand.net.nz, wanghai38@huawei.com, pablo@netfilter.org,
jiapeng.chong@linux.alibaba.com, xemul@openvz.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] net: fix information leakage in /proc/net/ptype
Date: Thu, 20 Jan 2022 10:50:09 +0000 [thread overview]
Message-ID: <164267580986.26718.1893811896925655041.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220118192013.1608432-1-liu3101@purdue.edu>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 18 Jan 2022 14:20:13 -0500 you wrote:
> In one net namespace, after creating a packet socket without binding
> it to a device, users in other net namespaces can observe the new
> `packet_type` added by this packet socket by reading `/proc/net/ptype`
> file. This is minor information leakage as packet socket is
> namespace aware.
>
> Add a net pointer in `packet_type` to keep the net namespace of
> of corresponding packet socket. In `ptype_seq_show`, this net pointer
> must be checked when it is not NULL.
>
> [...]
Here is the summary with links:
- [v2,net] net: fix information leakage in /proc/net/ptype
https://git.kernel.org/netdev/net/c/47934e06b656
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-01-20 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 19:20 Congyu Liu
2022-01-20 10:50 ` 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=164267580986.26718.1893811896925655041.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liu3101@purdue.edu \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rsanger@wand.net.nz \
--cc=wanghai38@huawei.com \
--cc=willemb@google.com \
--cc=xemul@openvz.org \
--cc=yajun.deng@linux.dev \
/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
Powered by JetHome