From: patchwork-bot+netdevbpf@kernel.org
To: Davide Caratti <dcaratti@redhat.com>
Cc: paul@paul-moore.com, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net, casey@schaufler-ca.com,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
xmu@redhat.com, omosnace@redhat.com
Subject: Re: [PATCH net v5] netlabel: fix RCU annotation for IPv4 options on socket creation
Date: Mon, 13 May 2024 22:10:28 +0000 [thread overview]
Message-ID: <171563822842.3982.11882395457554772824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <f4260d000a3a55b9e8b6a3b4e3fffc7da9f82d41.1715359817.git.dcaratti@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 10 May 2024 19:19:12 +0200 you wrote:
> Xiumei reports the following splat when netlabel and TCP socket are used:
>
> =============================
> WARNING: suspicious RCU usage
> 6.9.0-rc2+ #637 Not tainted
> -----------------------------
> net/ipv4/cipso_ipv4.c:1880 suspicious rcu_dereference_protected() usage!
>
> [...]
Here is the summary with links:
- [net,v5] netlabel: fix RCU annotation for IPv4 options on socket creation
https://git.kernel.org/netdev/net/c/8ec9897ec2e9
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:[~2024-05-13 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 17:19 [PATCH net v5] netlabel: fix RCU annotation for IPv4 options on socket creation Davide Caratti
2024-05-10 17:37 ` Casey Schaufler
2024-05-13 16:27 ` Paul Moore
2024-05-13 22:10 ` 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=171563822842.3982.11882395457554772824.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=xmu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).