public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: <netdev@vger.kernel.org>, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH ipsec-next 00/10] xfrm: fix most sparse warnings
Date: Fri, 13 Mar 2026 08:48:17 +0100	[thread overview]
Message-ID: <abPBQcgtrZh9sGCr@secunet.com> (raw)
In-Reply-To: <cover.1773051558.git.sd@queasysnail.net>

On Mon, Mar 09, 2026 at 11:32:33AM +0100, Sabrina Dubroca wrote:
> This series fixes most of the sparse warnings currently reported about
> RCU pointers for files under net/xfrm. There's no actual bug in the
> current code, we only need to use the correct helpers in each context.
> 
> Sabrina Dubroca (10):
>   xfrm: state: fix sparse warnings on xfrm_state_hold_rcu
>   xfrm: state: fix sparse warnings in xfrm_state_init
>   xfrm: state: fix sparse warnings around XFRM_STATE_INSERT
>   xfrm: state: add xfrm_state_deref_prot to state_by* walk under lock
>   xfrm: remove rcu/state_hold from xfrm_state_lookup_spi_proto
>   xfrm: state: silence sparse warnings during netns exit
>   xfrm: policy: fix sparse warnings in xfrm_policy_{init,fini}
>   xfrm: policy: silence sparse warning in xfrm_policy_unregister_afinfo
>   xfrm: add rcu_access_pointer to silence sparse warning for
>     xfrm_input_afinfo
>   xfrm: avoid RCU warnings around the per-netns netlink socket

Series applied, thanks a ot Sabrina!

  parent reply	other threads:[~2026-03-13  7:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 10:32 [PATCH ipsec-next 00/10] xfrm: fix most sparse warnings Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 01/10] xfrm: state: fix sparse warnings on xfrm_state_hold_rcu Sabrina Dubroca
2026-03-10 10:31   ` Leon Romanovsky
2026-03-10 11:33     ` Sabrina Dubroca
2026-03-10 18:20       ` Leon Romanovsky
2026-03-10 19:24         ` Florian Westphal
2026-03-10 19:45           ` Leon Romanovsky
2026-03-10 19:49             ` Florian Westphal
2026-03-10 20:10               ` Leon Romanovsky
2026-03-10 21:41                 ` Sabrina Dubroca
2026-03-11  7:36                   ` Leon Romanovsky
2026-03-12 14:36                     ` Sabrina Dubroca
2026-03-16 19:55                       ` Leon Romanovsky
2026-03-12  6:27                   ` Steffen Klassert
2026-03-09 10:32 ` [PATCH ipsec-next 02/10] xfrm: state: fix sparse warnings in xfrm_state_init Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 03/10] xfrm: state: fix sparse warnings around XFRM_STATE_INSERT Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 04/10] xfrm: state: add xfrm_state_deref_prot to state_by* walk under lock Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 05/10] xfrm: remove rcu/state_hold from xfrm_state_lookup_spi_proto Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 06/10] xfrm: state: silence sparse warnings during netns exit Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 07/10] xfrm: policy: fix sparse warnings in xfrm_policy_{init,fini} Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 08/10] xfrm: policy: silence sparse warning in xfrm_policy_unregister_afinfo Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 09/10] xfrm: add rcu_access_pointer to silence sparse warning for xfrm_input_afinfo Sabrina Dubroca
2026-03-09 10:32 ` [PATCH ipsec-next 10/10] xfrm: avoid RCU warnings around the per-netns netlink socket Sabrina Dubroca
2026-03-10 17:51 ` [PATCH ipsec-next 00/10] xfrm: fix most sparse warnings Simon Horman
2026-03-13  7:48 ` Steffen Klassert [this message]
2026-03-17  9:31   ` Steffen Klassert

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=abPBQcgtrZh9sGCr@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    /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