From: Miguel Gazquez <miguel.gazquez@bootlin.com>
To: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Andrey Ignatov <rdna@fb.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, Yinhao Hu <dddddd@hust.edu.cn>,
Kaiyan Mei <M202472210@hust.edu.cn>,
Dongliang Mu <dzm91@hust.edu.cn>
Subject: Re: [PATCH 5.10.y] bpf: Enforce expected_attach_type for tailcall compatibility
Date: Thu, 10 Sep 2026 11:34:05 +0200 [thread overview]
Message-ID: <4bbedc45-1f24-4124-87bb-a68da07b10e0@bootlin.com> (raw)
In-Reply-To: <2026-09-09-daily-reply-0031-bpf-tailcall-attach-type-5-10@kernel.org>
Hi
Le 09/09/2026 à 22:26, Sasha Levin a écrit :
>> The underlying issue goes beyond XDP though. Another example are programs
>> of type BPF_PROG_TYPE_CGROUP_SOCK_ADDR. sock_addr_is_valid_access() as well
>> as sock_addr_func_proto() have different logic depending on the programs'
>> expected_attach_type.
>
> Thanks for the 5.10.y backport of 4540aed51b12 ("bpf: Enforce
> expected_attach_type for tailcall compatibility"). Holding this until a 5.15.y
> version exists too, since fixes need to land on newer trees first.
>
Sorry I missed that there was no 5.15 backport, I sent it.
--
Miguel Gazquez, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-09-10 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 14:28 [PATCH 5.10.y] bpf: Enforce expected_attach_type for tailcall compatibility Miguel Gazquez (Schneider Electric)
2026-09-08 14:49 ` sashiko-bot
2026-09-09 20:26 ` Sasha Levin
2026-09-10 9:34 ` Miguel Gazquez [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=4bbedc45-1f24-4124-87bb-a68da07b10e0@bootlin.com \
--to=miguel.gazquez@bootlin.com \
--cc=M202472210@hust.edu.cn \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dddddd@hust.edu.cn \
--cc=dzm91@hust.edu.cn \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdna@fb.com \
--cc=sashal@kernel.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.