From: Simon Horman <horms@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Daniel Zahka <daniel.zahka@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: psp: select CONFIG_SKB_EXTENSIONS
Date: Tue, 17 Feb 2026 14:54:07 +0000 [thread overview]
Message-ID: <aZSBD6Au8FJPV1Vh@horms.kernel.org> (raw)
In-Reply-To: <20260216105500.2382181-1-arnd@kernel.org>
On Mon, Feb 16, 2026 at 11:54:54AM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> psp now uses skb extensions, failing to build when that is disabled:
>
> In file included from include/net/psp.h:7,
> from net/psp/psp_sock.c:9:
> include/net/psp/functions.h: In function '__psp_skb_coalesce_diff':
> include/net/psp/functions.h:60:13: error: implicit declaration of function 'skb_ext_find'; did you mean 'skb_ext_copy'? [-Wimplicit-function-declaration]
> 60 | a = skb_ext_find(one, SKB_EXT_PSP);
> | ^~~~~~~~~~~~
> | skb_ext_copy
> include/net/psp/functions.h:60:31: error: 'SKB_EXT_PSP' undeclared (first use in this function)
> 60 | a = skb_ext_find(one, SKB_EXT_PSP);
> | ^~~~~~~~~~~
> include/net/psp/functions.h:60:31: note: each undeclared identifier is reported only once for each function it appears in
> include/net/psp/functions.h: In function '__psp_sk_rx_policy_check':
> include/net/psp/functions.h:94:53: error: 'SKB_EXT_PSP' undeclared (first use in this function)
> 94 | struct psp_skb_ext *pse = skb_ext_find(skb, SKB_EXT_PSP);
> | ^~~~~~~~~~~
> net/psp/psp_sock.c: In function 'psp_sock_recv_queue_check':
> net/psp/psp_sock.c:164:41: error: 'SKB_EXT_PSP' undeclared (first use in this function)
> 164 | pse = skb_ext_find(skb, SKB_EXT_PSP);
> | ^~~~~~~~~~~
>
> Select the Kconfig symbol as we do from its other users.
>
> Fixes: 6b46ca260e22 ("net: psp: add socket security association code")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> net/psp/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/psp/Kconfig b/net/psp/Kconfig
> index 371e8771f3bd..84d6b0f25460 100644
> --- a/net/psp/Kconfig
> +++ b/net/psp/Kconfig
> @@ -6,6 +6,7 @@ config INET_PSP
> bool "PSP Security Protocol support"
> depends on INET
> select SKB_DECRYPTED
> + select SKB_EXTENSIONS
> select SOCK_VALIDATE_XMIT
> help
> Enable kernel support for the PSP Security Protocol (PSP).
I agree that the is written in such a way that it assumes this is available.
And select is an appropriate way to do so.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-02-17 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 10:54 [PATCH] net: psp: select CONFIG_SKB_EXTENSIONS Arnd Bergmann
2026-02-17 14:54 ` Simon Horman [this message]
2026-02-17 18:45 ` Daniel Zahka
2026-02-18 1:20 ` patchwork-bot+netdevbpf
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=aZSBD6Au8FJPV1Vh@horms.kernel.org \
--to=horms@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@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