From: patchwork-bot+netdevbpf@kernel.org
To: Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, leon@kernel.org
Subject: Re: [PATCH net-next v2] scm: fix MSG_CTRUNC setting condition for SO_PASSSEC
Date: Wed, 15 Mar 2023 08:30:17 +0000 [thread overview]
Message-ID: <167886901731.1055.14504007440539285248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313113211.178010-1-aleksandr.mikhalitsyn@canonical.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 13 Mar 2023 12:32:11 +0100 you wrote:
> Currently, kernel would set MSG_CTRUNC flag if msg_control buffer
> wasn't provided and SO_PASSCRED was set or if there was pending SCM_RIGHTS.
>
> For some reason we have no corresponding check for SO_PASSSEC.
>
> In the recvmsg(2) doc we have:
> MSG_CTRUNC
> indicates that some control data was discarded due to lack
> of space in the buffer for ancillary data.
>
> [...]
Here is the summary with links:
- [net-next,v2] scm: fix MSG_CTRUNC setting condition for SO_PASSSEC
https://git.kernel.org/netdev/net-next/c/a02d83f9947d
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:[~2023-03-15 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 11:32 [PATCH net-next v2] scm: fix MSG_CTRUNC setting condition for SO_PASSSEC Alexander Mikhalitsyn
2023-03-13 11:40 ` Aleksandr Mikhalitsyn
2023-03-13 20:43 ` Paul Moore
2023-03-14 11:06 ` Aleksandr Mikhalitsyn
2023-03-15 8:30 ` 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=167886901731.1055.14504007440539285248.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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