From: Shakeel Butt <shakeel.butt@linux.dev>
To: Tejun Heo <tj@kernel.org>
Cc: "Qing Ming" <a0yami@mailbox.org>,
"Josef Bacik" <josef@toxicpanda.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Muchun Song" <muchun.song@linux.dev>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Hao Luo" <haoluo@google.com>, "Yosry Ahmed" <yosry@kernel.org>,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v2] cgroup/rstat: validate cpu before css_rstat_cpu() access
Date: Mon, 18 May 2026 16:07:44 -0700 [thread overview]
Message-ID: <agubZePrBmStHxhH@linux.dev> (raw)
In-Reply-To: <64f59b64664f769661a8b8cd587c85f8@kernel.org>
On Mon, May 18, 2026 at 09:36:36AM -1000, Tejun Heo wrote:
> Hello,
>
> > Qing Ming (1):
> > cgroup/rstat: validate cpu before css_rstat_cpu() access
>
> Applied to cgroup/for-7.1-fixes.
>
> In hindsight, we should have added a separate kfunc wrapper from the
> start instead of tagging css_rstat_updated() with __bpf_kfunc directly,
> which would have avoided the rename. Oh well, it is what it is.
Is it frown upon to change the kfunc signature or remove __bpf_kfunc from a
function? I am assuming we can but better not to, correct?
next prev parent reply other threads:[~2026-05-18 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260515122952.59209-1-a0yami@mailbox.org>
2026-05-16 7:08 ` [PATCH v2] cgroup/rstat: validate cpu before css_rstat_cpu() access Qing Ming
2026-05-18 19:36 ` Tejun Heo
2026-05-18 23:07 ` Shakeel Butt [this message]
2026-05-18 23:40 ` Tejun Heo
2026-05-25 13:53 ` 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=agubZePrBmStHxhH@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=a0yami@mailbox.org \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=haoluo@google.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=tj@kernel.org \
--cc=yosry@kernel.org \
/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