From: Yonghong Song <yonghong.song@linux.dev>
To: "malin (R)" <malin89@huawei.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
cenxianlong <cenxianlong@huawei.com>,
Chenzhe <chenzhe@huawei.com>,
"ameryhung@gmail.com" <ameryhung@gmail.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
YiFei Zhu <zhuyifei@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bpf: Tighten cgroup storage cookie checks for prog arrays
Date: Mon, 1 Jun 2026 20:31:05 -0700 [thread overview]
Message-ID: <ac9096c9-dee7-4bb0-9741-6758fc278a48@linux.dev> (raw)
In-Reply-To: <b160365f172b48f395e7edb7e1f879b9@huawei.com>
On 6/1/26 6:51 PM, malin (R) wrote:
> Hello Yonghong,
>
>> The patch looks okay to me. But can you add a selftest for this?
> OK, we will send v2 patch with added selftest.
>
> By the way, as the AI review bot found, this patch idea is already proposed by Amery.
> https://lore.kernel.org/bpf/20251203195050.3215728-1-ameryhung@gmail.com/
>
> Should I add something like Suggested-by for him or something else?
Change 'him' to 'her'.
I think you can mention this in commit message.
>
> Thanks
> Lin
next prev parent reply other threads:[~2026-06-02 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 1:51 malin (R)
2026-06-02 3:31 ` Yonghong Song [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-02 8:17 malin (R)
2026-06-01 10:56 malin (R)
2026-06-01 9:51 Lin Ma
2026-06-01 10:35 ` bot+bpf-ci
2026-06-01 16:00 ` Yonghong Song
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=ac9096c9-dee7-4bb0-9741-6758fc278a48@linux.dev \
--to=yonghong.song@linux.dev \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cenxianlong@huawei.com \
--cc=chenzhe@huawei.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malin89@huawei.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=zhuyifei@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome