netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
	jiang.wang@bytedance.com, cong.wang@bytedance.com,
	jakub@cloudflare.com, john.fastabend@gmail.com,
	daniel@iogearbox.net, lmb@cloudflare.com
Subject: Re: [Patch bpf-next] unix_bpf: check socket type in unix_bpf_update_proto()
Date: Tue, 03 Aug 2021 11:00:05 +0000	[thread overview]
Message-ID: <162798840569.8237.10177064889058148886.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210731195038.8084-1-xiyou.wangcong@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Sat, 31 Jul 2021 12:50:38 -0700 you wrote:
> From: Cong Wang <cong.wang@bytedance.com>
> 
> As of now, only AF_UNIX datagram socket supports sockmap.
> But unix_proto is shared for all kinds of AF_UNIX sockets,
> so we have to check the socket type in
> unix_bpf_update_proto() to explicitly reject other types,
> otherwise they could be added into sockmap too.
> 
> [...]

Here is the summary with links:
  - [bpf-next] unix_bpf: check socket type in unix_bpf_update_proto()
    https://git.kernel.org/bpf/bpf-next/c/83f31535565c

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-08-03 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 19:50 [Patch bpf-next] unix_bpf: check socket type in unix_bpf_update_proto() Cong Wang
2021-08-02  9:00 ` Jakub Sitnicki
2021-08-03 11:00 ` 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=162798840569.8237.10177064889058148886.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=cong.wang@bytedance.com \
    --cc=daniel@iogearbox.net \
    --cc=jakub@cloudflare.com \
    --cc=jiang.wang@bytedance.com \
    --cc=john.fastabend@gmail.com \
    --cc=lmb@cloudflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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).