From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
bpf@vger.kernel.org, memxor@gmail.com,
Yingke Xiao <inkxiao12@gmail.com>
Subject: Re: [PATCH 6.12.y] bpf: Add tracepoints with null-able arguments (CVE-2024-56702)
Date: Fri, 20 Nov 2026 15:39:04 -0500 [thread overview]
Message-ID: <2026-11-20-1-daily-reply-0015@kernel.org> (raw)
In-Reply-To: <CAMcAce-4MeO8rpx2rvDu77r-OpbFd9k0geOs8wZBoaMbYVkpDw@mail.gmail.com>
> [ Upstream commit c83e2d970bae ("bpf: Add tracepoints with null-able
> arguments") ]
I can't take this one:
- The patch is whitespace-damaged and does not apply.
- It adds 5 of the entries c83e2d970bae ("bpf: Add tracepoints with
null-able arguments") adds, with no reason given for leaving the rest out.
- It lacks the "From: Jiri Olsa" line and the upstream sign-offs, and
carries a Signed-off-by from Kumar that is not on the upstream commit.
- CVE-2024-56702 is cb4158ce8ec8 ("bpf: Mark raw_tp arguments with
PTR_MAYBE_NULL"), not this commit.
Please send a backport of the full upstream commit with git send-email.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-20 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 16:45 [PATCH 6.12.y] bpf: Add tracepoints with null-able arguments (CVE-2024-56702) Yingke Xiao
2026-11-20 20:39 ` 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-20-1-daily-reply-0015@kernel.org \
--to=sashal@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=inkxiao12@gmail.com \
--cc=memxor@gmail.com \
--cc=stable@vger.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