From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: 王贇 <yun.wang@linux.alibaba.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Paul Mackerras" <paulus@samba.org>,
"Jisheng Zhang" <jszhang@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
live-patching@vger.kernel.org, linux-riscv@lists.infradead.org,
"Miroslav Benes" <mbenes@suse.cz>,
"Joe Lawrence" <joe.lawrence@redhat.com>,
"Helge Deller" <deller@gmx.de>,
x86@kernel.org, linux-csky@vger.kernel.org,
"Ingo Molnar" <mingo@redhat.com>,
"Petr Mladek" <pmladek@suse.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Jiri Kosina" <jikos@kernel.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Borislav Petkov" <bp@alien8.de>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Guo Ren" <guoren@kernel.org>,
"Colin Ian King" <colin.king@canonical.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2] tracing: Have all levels of checks prevent recursion
Date: Mon, 18 Oct 2021 17:55:14 -0400 [thread overview]
Message-ID: <20211018175505.3e19155a@gandalf.local.home> (raw)
In-Reply-To: <20211018154412.09fcad3c@gandalf.local.home>
On Mon, 18 Oct 2021 15:44:12 -0400
Steven Rostedt <rostedt@goodmis.org> (by way of Steven Rostedt
<rostedt@goodmis.org>) wrote:
> [
> Linus,
> I have patches that clean this up that are not marked for stable, but
> will depend on this patch. As I already have commits in my next queue,
> I can do one of the following:
>
> 1. Cherry pick this from my urgent tree, and build everything on top.
> 2. Add this on top of the mainline tag my next branch is based on and
> merge it.
> 3. Add this to my next branch, and have it go in at the next merge
> window.
Hmm, I take this back. Although the clean up affects the same code block,
the updates don't actually conflict. (Although, if I do update the comment
that Petr asked, that will conflict. But nothing you can't handle ;-)
I'll start running this change through my tests and post it separately.
-- Steve
> ]
prev parent reply other threads:[~2021-10-18 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 19:44 [PATCH v2] tracing: Have all levels of checks prevent recursion Steven Rostedt
2021-10-18 21:55 ` Steven Rostedt [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=20211018175505.3e19155a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=colin.king@canonical.com \
--cc=deller@gmx.de \
--cc=guoren@kernel.org \
--cc=hpa@zytor.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=jszhang@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yun.wang@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).