From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
Taegu Ha <hataegu0826@gmail.com>,
Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH 7.1.y] bpf: reject overlarge global subprog argument sizes
Date: Thu, 27 Aug 2026 01:17:51 -0400 [thread overview]
Message-ID: <20260827050834.10001.stable-daily@kernel.org> (raw)
In-Reply-To: <20260825142432.2347543-1-hataegu0826@gmail.com>
> [ Upstream commit de36adca634634c205a9eb8b56a28175ab7abf5f ]
>
> Global subprogram argument checking derives generic pointer sizes from BTF
> and passes the resolved size to check_mem_reg() as a u32. The access-size
> validation path then uses a signed int, and stack pointers negate the value
> before calling check_helper_mem_access().
Queued for 7.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-27 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 19:00 [STABLE REQUEST] bpf: backport de36adca6346 to 7.1.y 하태구
2026-08-25 8:25 ` Greg KH
2026-08-25 14:24 ` [PATCH 7.1.y] bpf: reject overlarge global subprog argument sizes Taegu Ha
2026-08-27 5:17 ` 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=20260827050834.10001.stable-daily@kernel.org \
--to=sashal@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hataegu0826@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yonghong.song@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