From: patchwork-bot+netdevbpf@kernel.org
To: David Brazdil <dbrazdil@google.com>
Cc: selinux@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, paul@paul-moore.com,
stephen.smalley.work@gmail.com, eparis@parisplace.org,
jeffv@google.com, adelva@google.com
Subject: Re: [PATCH v2] selinux: vsock: Set SID for socket returned by accept()
Date: Fri, 19 Mar 2021 21:00:09 +0000 [thread overview]
Message-ID: <161618760912.12397.14174236493108534163.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210319130541.2188184-1-dbrazdil@google.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 19 Mar 2021 13:05:41 +0000 you wrote:
> For AF_VSOCK, accept() currently returns sockets that are unlabelled.
> Other socket families derive the child's SID from the SID of the parent
> and the SID of the incoming packet. This is typically done as the
> connected socket is placed in the queue that accept() removes from.
>
> Reuse the existing 'security_sk_clone' hook to copy the SID from the
> parent (server) socket to the child. There is no packet SID in this
> case.
>
> [...]
Here is the summary with links:
- [v2] selinux: vsock: Set SID for socket returned by accept()
https://git.kernel.org/netdev/net/c/1f935e8e72ec
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:[~2021-03-19 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 13:05 [PATCH v2] selinux: vsock: Set SID for socket returned by accept() David Brazdil
2021-03-19 13:30 ` David Brazdil
2021-03-19 21: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=161618760912.12397.14174236493108534163.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adelva@google.com \
--cc=dbrazdil@google.com \
--cc=eparis@parisplace.org \
--cc=jeffv@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@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).