From: Jianlin Lv <iecedge@gmail.com>
To: rostedt@goodmis.org, alison.schofield@intel.com,
davidgow@google.com, thunder.leizhen@huawei.com
Cc: iecedge@gmail.com, jianlv@ebay.com, linux-kernel@vger.kernel.org
Subject: [PATCH] tracepoint: Allow livepatch module add trace event
Date: Wed, 2 Nov 2022 16:02:36 +0000 [thread overview]
Message-ID: <20221102160236.11696-1-iecedge@gmail.com> (raw)
In the case of keeping the system running, the preferred method for
tracing the kernel is dynamic tracing (kprobe), but the drawback of
this method is that events are lost, especially when tracing packages
in the network stack.
Livepatching provides a potential solution, which is to reimplement the
function you want to replace and insert a static tracepoint.
In such a way, custom stable static tracepoints can be expanded without
rebooting the system.
Signed-off-by: Jianlin Lv <iecedge@gmail.com>
---
kernel/tracepoint.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
index f23144af5743..8d1507dd0724 100644
--- a/kernel/tracepoint.c
+++ b/kernel/tracepoint.c
@@ -571,8 +571,8 @@ static void for_each_tracepoint_range(
bool trace_module_has_bad_taint(struct module *mod)
{
return mod->taints & ~((1 << TAINT_OOT_MODULE) | (1 << TAINT_CRAP) |
- (1 << TAINT_UNSIGNED_MODULE) |
- (1 << TAINT_TEST));
+ (1 << TAINT_UNSIGNED_MODULE) | (1 << TAINT_TEST) |
+ (1 << TAINT_LIVEPATCH));
}
static BLOCKING_NOTIFIER_HEAD(tracepoint_notify_list);
--
2.25.1
next reply other threads:[~2022-11-02 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:02 Jianlin Lv [this message]
2022-11-14 17:20 ` [PATCH] tracepoint: Allow livepatch module add trace event Steven Rostedt
2022-11-14 17:23 ` Steven Rostedt
2022-11-15 2:38 ` Jianlin Lv
2022-11-15 3:02 ` Steven Rostedt
2022-11-15 15:07 ` Masami Hiramatsu
2022-11-15 15:18 ` Steven Rostedt
2022-12-23 4:52 ` Jianlin Lv
2022-12-23 5:08 ` Steven Rostedt
2023-02-17 1:47 ` Steven Rostedt
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=20221102160236.11696-1-iecedge@gmail.com \
--to=iecedge@gmail.com \
--cc=alison.schofield@intel.com \
--cc=davidgow@google.com \
--cc=jianlv@ebay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=thunder.leizhen@huawei.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