From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
syzbot+2d9f5f948c31dcb7745e@syzkaller.appspotmail.com,
paul@paul-moore.com, stephen.smalley.work@gmail.com,
omosnace@redhat.com, selinux@vger.kernel.org, kuniyu@amazon.com,
brianvv@google.com
Subject: Re: [PATCH net] selinux: use sk_to_full_sk() in selinux_ip_output()
Date: Sat, 30 Nov 2024 21:50:33 +0000 [thread overview]
Message-ID: <173300343374.2487269.7082262124805020262.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241126145911.4187198-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 Nov 2024 14:59:11 +0000 you wrote:
> In blamed commit, TCP started to attach timewait sockets to
> some skbs.
>
> syzbot reported that selinux_ip_output() was not expecting them yet.
>
> Note that using sk_to_full_sk() is still allowing the
> following sk_listener() check to work as before.
>
> [...]
Here is the summary with links:
- [net] selinux: use sk_to_full_sk() in selinux_ip_output()
https://git.kernel.org/netdev/net/c/eedcad2f2a37
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-11-30 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 14:59 [PATCH net] selinux: use sk_to_full_sk() in selinux_ip_output() Eric Dumazet
2024-11-26 15:54 ` Paul Moore
2024-11-27 3:49 ` Kuniyuki Iwashima
2024-11-30 21:50 ` patchwork-bot+netdevbpf [this message]
2024-12-03 20:50 ` Paul Moore
2024-12-04 0:55 ` Jakub Kicinski
2024-12-04 3:44 ` Paul Moore
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=173300343374.2487269.7082262124805020262.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=syzbot+2d9f5f948c31dcb7745e@syzkaller.appspotmail.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).