From: "Eddy_Wu@trendmicro.com" <Eddy_Wu@trendmicro.com>
To: "peterz@infradead.org" <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"naveen.n.rao@linux.ibm.com" <naveen.n.rao@linux.ibm.com>,
"anil.s.keshavamurthy@intel.com" <anil.s.keshavamurthy@intel.com>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"cameron@moodycamel.com" <cameron@moodycamel.com>,
"oleg@redhat.com" <oleg@redhat.com>,
"will@kernel.org" <will@kernel.org>,
"paulmck@kernel.org" <paulmck@kernel.org>,
"systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: RE: [PATCH v5 00/21] kprobes: Unify kretprobe trampoline handlers and make kretprobe lockless
Date: Tue, 8 Sep 2020 11:15:14 +0000 [thread overview]
Message-ID: <dd1b7b1fdbd84d20ad06abf0c06b4747@trendmicro.com> (raw)
In-Reply-To: <20200908103736.GP1362448@hirez.programming.kicks-ass.net>
> From: peterz@infradead.org <peterz@infradead.org>
>
> I'm now trying and failing to reproduce.... I can't seem to make it use
> int3 today. It seems to want to use ftrace or refuses everything. I'm
> probably doing it wrong.
>
You can turn off CONFIG_KPROBES_ON_FTRACE (and also sysctl debug.kprobes-optimization) to make it use int3 handler
TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
For details about what personal information we collect and why, please see our Privacy Notice on our website at: Read privacy policy<http://www.trendmicro.com/privacy>
next prev parent reply other threads:[~2020-09-08 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <159870598914.1229682.15230803449082078353.stgit@devnote2>
[not found] ` <20200901190808.GK29142@worktop.programming.kicks-ass.net>
[not found] ` <20200902093739.8bd13603380951eaddbcd8a5@kernel.org>
[not found] ` <20200902070226.GG2674@hirez.programming.kicks-ass.net>
[not found] ` <20200902171755.b126672093a3c5d1b3a62a4f@kernel.org>
[not found] ` <20200902093613.GY1362448@hirez.programming.kicks-ass.net>
[not found] ` <20200902221926.f5cae5b4ad00b8d8f9ad99c7@kernel.org>
[not found] ` <20200902134252.GH1362448@hirez.programming.kicks-ass.net>
2020-09-03 1:39 ` Masami Hiramatsu
2020-09-03 2:02 ` Masami Hiramatsu
2020-09-07 17:44 ` Frank Ch. Eigler
2020-09-08 2:55 ` Masami Hiramatsu
2020-09-08 10:37 ` peterz
2020-09-08 11:15 ` Eddy_Wu [this message]
2020-09-08 11:33 ` peterz
2020-09-08 15:09 ` Masami Hiramatsu
2020-09-09 5:28 ` Masami Hiramatsu
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=dd1b7b1fdbd84d20ad06abf0c06b4747@trendmicro.com \
--to=eddy_wu@trendmicro.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=cameron@moodycamel.com \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=systemtap@sourceware.org \
--cc=will@kernel.org \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).