From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Date: Thu, 30 Sep 2021 23:37:08 +0000 Subject: Re: [PATCH -tip v11 00/27] kprobes: Fix stacktrace with kretprobes on x86 Message-Id: <20210930193708.3b2caf23@oasis.local.home> List-Id: References: <163163030719.489837.2236069935502195491.stgit@devnote2> <20210929112408.35b0ffe06b372533455d890d@kernel.org> <874ka17t8s.ffs@tglx> <20210930172206.1a34279b@oasis.local.home> <87wnmx64mn.ffs@tglx> <20211001082733.236bee605f506b2b62c055ef@kernel.org> In-Reply-To: <20211001082733.236bee605f506b2b62c055ef@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Masami Hiramatsu Cc: Thomas Gleixner , Alexei Starovoitov , Linus Torvalds , Josh Poimboeuf , Ingo Molnar , X86 ML , LKML , bpf , Jakub Kicinski , Ingo Molnar , Borislav Petkov , Peter Zijlstra , Kernel Team , linux-ia64@vger.kernel.org, Abhishek Sagar , Andrii Nakryiko , Paul McKenney On Fri, 1 Oct 2021 08:27:33 +0900 Masami Hiramatsu wrote: > Let me explain how the patches are usually merged. > > - kernel/kprobes.c related patches go through the tip tree. > - kernel/trace/* patches go through the tracing tree. And arch/*/kprobe* usually goes through tip as well. > > So traditionally(?) I think this series go through the tip tree, > but since the biggest user of kprobes is tracing and the kprobes fix > now involves tree-wide fixes as you can see in this series, I think > it is a good timing to move kprobes to tracing tree. I'll pick it up and take the burden off of Thomas. Just to confirm, this is for the next merge window, right? -- Steve