[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6387B54B-7524-4AB9-AB05-4AB529353EF4@kernel.org>
Date: Fri, 19 Dec 2025 17:33:24 +0900
From: Kees Cook <kees@...nel.org>
To: Tejun Heo <tj@...nel.org>, Chen Ridong <chenridong@...weicloud.com>
CC: Michal Koutný <mkoutny@...e.com>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Johannes Weiner <hannes@...xchg.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>
Subject: Re: [PATCH 3/4] cgroup: Use __counted_by for cgroup::ancestors
On December 19, 2025 1:09:42 AM GMT+09:00, Tejun Heo <tj@...nel.org> wrote:
>On Thu, Dec 18, 2025 at 03:09:32PM +0800, Chen Ridong wrote:
>> Note that this level may already be used in existing BPF programs (e.g.,
>> tools/testing/selftests/bpf/progs/task_ls_uptr.c). Do we need to consider compatibility here?
>
>That's a good point. Is __counted_by instrumentation tied to some compiler
>flag? If so, might as well make it an optional extra field specifically for
>the annotation rather than changing the meaning of an existing field.
>
>Thanks.
>
CONFIG_FORTIFY_SOURCE and CONFIG_UBSAN_BOUNDS use the information for instrumentation.
--
Kees Cook
Powered by blists - more mailing lists