From: Al Viro <viro@ZenIV.linux.org.uk>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dmitry Safonov <0x7f454c46@gmail.com>, linux-kernel@vger.kernel.org
Subject: [RFC] apparent bogosity in unregister_ftrace_function_probe_func()
Date: Sat, 27 Jan 2018 03:17:06 +0000 [thread overview]
Message-ID: <20180127031706.GE13338@ZenIV.linux.org.uk> (raw)
It contains something very odd:
func_g.type = filter_parse_regex(glob, strlen(glob),
&func_g.search, ¬);
func_g.len = strlen(func_g.search);
func_g.search = glob;
/* we do not support '!' for function probes */
if (WARN_ON(not))
return -EINVAL;
What the hell is the last assignment for? After that call of
filter_parse_regex() we could have func_g.search not equal to glob
only if glob started with '!' or '*'. In the former case we would've
buggered off with -EINVAL (not = 1). In the latter we would've set
func_g.search equal to glob + 1, calculated the length of that thing
in func_g.len and proceeded to reset func_g.search back to glob.
Suppose the glob is e.g. *foo*. We end up with
func_g.type = MATCH_MIDDLE_ONLY;
func_g.len = 3;
func_g.search = "*foo";
Feeding that to ftrace_match_record() will not do anything sane - we
will be looking for names containing "*foo" (->len is ignored for that
one).
Incidentally, shouldn't filter_parse_regex("*[ab]", 5, &s, ¬)
end up with s = "*[ab]"? We are returning MATCH_GLOB, after all,
so we want the entire pattern there... I would've assumed that
this is what the code in unregister_ftrace_function_probe_func()
is trying to compensate for, the first oddity predates MATCH_GLOB...
In any case, that should be done in filter_parse_regex() itself -
there are other callers that don't have such compensation and
it does the wrong thing for MATCH_MIDDLE_ONLY and MATCH_END_ONLY
cases...
That started in commit 3ba009297149fa45956c33ab5de7c5f4da1f28b8
Author: Dmitry Safonov <0x7f454c46@gmail.com>
Date: Tue Sep 29 19:46:14 2015 +0300
ftrace: Introduce ftrace_glob structure
without any explanation -
- type = filter_parse_regex(glob, strlen(glob), &search, ¬);
- len = strlen(search);
+ func_g.type = filter_parse_regex(glob, strlen(glob),
+ &func_g.search, ¬);
+ func_g.len = strlen(func_g.search);
+ func_g.search = glob;
Note in the same commit
- type = filter_parse_regex(glob, strlen(glob), &search, ¬);
- len = strlen(search);
+ func_g.type = filter_parse_regex(glob, strlen(glob),
+ &func_g.search, ¬);
+ func_g.len = strlen(func_g.search);
nearby (in register_ftrace_function_probe()).
What am I missing here?
next reply other threads:[~2018-01-27 3:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 3:17 Al Viro [this message]
2018-01-27 13:59 ` Dmitry Safonov
2018-01-27 17:07 ` Al Viro
2018-01-28 10:31 ` Steven Rostedt
2018-01-29 13:59 ` Masami Hiramatsu
2018-02-05 22:54 ` Steven Rostedt
2018-02-06 1:25 ` Dmitry Safonov
2018-02-06 2:26 ` Masami Hiramatsu
2018-02-06 2:40 ` Steven Rostedt
2018-02-06 2:44 ` Dmitry Safonov
2018-02-06 2:48 ` Steven Rostedt
2018-02-06 2:53 ` Dmitry Safonov
2018-01-29 13:49 ` 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=20180127031706.GE13338@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=0x7f454c46@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®