From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@kernel.org>,
tianyaxiong@kylinos.cn, rostedt@goodmis.org, mhiramat@kernel.org,
"André Freitag" <andre@brainchimps.com>
Subject: Re: [stable request] 6.18: tracing/kprobes: Skip setup_boot_kprobe_events() when no cmdline event
Date: Sat, 21 Nov 2026 10:27:43 -0500 [thread overview]
Message-ID: <2026-11-21-1-daily-reply-0015@kernel.org> (raw)
In-Reply-To: <CAEF_Rj8MFeLOXr+08ykGeASYXc7gCFwNuABiZDm3oC1DxCwoZQ@mail.gmail.com>
> please consider this upstream commit for 6.18.y:
>
> 2cdfe39dc944 ("tracing/kprobes: Skip setup_boot_kprobe_events() when
> no cmdline event")
This is a boot-time optimization rather than a fix, and it has no Fixes: or
stable tag upstream, so I'm going to pass on it for 6.18.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-21 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEF_Rj9AGCqWh4TeX0y1sOoF5g7jEh_Xhp_EnKPSEQ9thU3mmg@mail.gmail.com>
2026-11-21 2:03 ` [stable request] 6.18: tracing/kprobes: Skip setup_boot_kprobe_events() when no cmdline event André Freitag
2026-11-21 15:27 ` 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-21-1-daily-reply-0015@kernel.org \
--to=sashal@kernel.org \
--cc=andre@brainchimps.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tianyaxiong@kylinos.cn \
/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