From: Greg KH <gregkh@linuxfoundation.org>
To: Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
stable@vger.kernel.org, sashal@kernel.org,
DL Linux Open Source Team <linux-open-source@crowdstrike.com>,
Jiri Olsa <olsajiri@gmail.com>
Subject: Re: [STABLE REQUEST] ftrace: deprecate the ftrace_enabled disable switch
Date: Wed, 4 Nov 2026 11:02:06 -0500 [thread overview]
Message-ID: <2026110439-pork-mossy-0316@gregkh> (raw)
In-Reply-To: <CAOu3gNiggAdifeAUpycoO-zGKb0k2-nZqWrtDXMXm_HXT8L1Vw@mail.gmail.com>
On Wed, Nov 04, 2026 at 10:43:37AM -0500, Andrey Grodzovsky wrote:
> On Wed, Nov 4, 2026 at 8:39 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Tue, 3 Nov 2026 21:51:42 -0500
> > Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com> wrote:
> >
> > > Hi Steve, coming back to this topic (sorry it took me a while - other
> > > work related stuff kept me busy). Are you still willing to accept [1]
> > > upstream ? If yes, can you also please clarify why only the first 2
> > > patches and not the third, selftest patch?
> >
> > I was thinking for backporting purposes. The selftest patch is fine, but
> > not something that needs to be backported.
> >
> > -- Steve
>
> Ok, so just to clear my own confusion: do we want to directly present
> this to stable as a backport fixing a bug, or go through merge to
> mainline first and then only backport? If we do want to take it into
> mainline then I think the selftest patch is beneficial especially
> because Jiri found some case that breaks there that needs furhter
> invistigation [1].
We can not take patches in stable that are not upstream first unless
there is a VERY good reason why that can not happen.
thanks,
greg k-h
next prev parent reply other threads:[~2026-11-04 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 21:30 [STABLE REQUEST] ftrace: deprecate the ftrace_enabled disable switch Andrey Grodzovsky
2026-08-20 22:20 ` Steven Rostedt
2026-08-21 15:04 ` Andrey Grodzovsky
2026-11-04 2:51 ` Andrey Grodzovsky
2026-11-04 13:39 ` Steven Rostedt
2026-11-04 15:43 ` Andrey Grodzovsky
2026-11-04 16:02 ` Greg KH [this message]
2026-11-04 17:30 ` Steven Rostedt
2026-11-04 17:32 ` Andrey Grodzovsky
2026-11-05 21:22 ` Andrey Grodzovsky
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=2026110439-pork-mossy-0316@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=linux-open-source@crowdstrike.com \
--cc=olsajiri@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--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