From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: Sasha Levin <sashal@kernel.org>,
asatsuyu.liu@gmail.com, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, puranjay@kernel.org,
stable@vger.kernel.org, vadim.fedorenko@linux.dev
Subject: Re: [PATCH 6.18.y 0/2] bpf: Make KF_TRUSTED_ARGS the default for all kfuncs
Date: Thu, 19 Nov 2026 11:08:13 -0500 [thread overview]
Message-ID: <2026-11-19-1-daily-reply-0011@kernel.org> (raw)
In-Reply-To: <20261118142654.3098395-1-asatsuyu.liu@gmail.com>
> Here is a direct backport of upstream commit
> 1a5c01d2508a ("bpf: Make KF_TRUSTED_ARGS the default for all kfuncs")
> to v6.18.64.
This changes verifier behaviour for every kfunc: programs that load today
(for instance NULL arguments to the netfilter conntrack kfuncs) will be
rejected. The series also leaves out the other selftest fixes that went in
with 1a5c01d2508a ("bpf: Make KF_TRUSTED_ARGS the default for all kfuncs").
I'm holding this until a BPF maintainer acks it for stable.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-19 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 10:17 [RFC PATCH 6.18.y 0/1] bpf: reject NULL arguments to four kfuncs asatsuyu.liu
2026-11-18 10:17 ` [RFC PATCH 6.18.y 1/1] bpf: Reject " asatsuyu.liu
2026-11-18 10:40 ` sashiko-bot
2026-11-18 10:40 ` [RFC PATCH 6.18.y 0/1] bpf: reject " Greg KH
2026-11-18 14:26 ` [PATCH 6.18.y 0/2] bpf: Make KF_TRUSTED_ARGS the default for all kfuncs asatsuyu.liu
2026-11-18 14:26 ` [PATCH 6.18.y 1/2] " asatsuyu.liu
2026-11-18 14:26 ` [PATCH 6.18.y 2/2] selftests: bpf: Fix test_bpf_nf for trusted args becoming default asatsuyu.liu
2026-11-19 16:08 ` Sasha Levin [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=2026-11-19-1-daily-reply-0011@kernel.org \
--to=sashal@kernel.org \
--cc=asatsuyu.liu@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=puranjay@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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