From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>, Al Viro <viro@ZenIV.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: Fix event filters and triggers to handle negative numbers
Date: Thu, 28 Feb 2019 09:11:37 +0000 [thread overview]
Message-ID: <f0929165-bc75-c13a-7a20-43262ef8a496@virtuozzo.com> (raw)
In-Reply-To: <20180823204849.3b4aede3@vmware.local.home>
ping, looks like the patch was lost
On 8/24/18 3:48 AM, Steven Rostedt wrote:
> On Thu, 23 Aug 2018 13:25:34 +0300
> Pavel Tikhomirov <ptikhomirov@virtuozzo.com> wrote:
>
>> Then tracing syscall exit event it is extremely useful to filter exit
>> codes equal to some negative value, to react only to required errors.
>> But negative numbers does not work:
>>
>> [root@snorch sys_exit_read]# echo "ret == -1" > filter
>> bash: echo: write error: Invalid argument
>> [root@snorch sys_exit_read]# cat filter
>> ret == -1
>> ^
>> parse_error: Invalid value (did you forget quotes)?
>
> Thanks for the patch. I'll apply it and then start testing it!
>
> -- Steve
>
>>
>> Similar thing happens when setting triggers.
>>
>> These is a regression in v4.17 introduced by the commit mentioned below,
>> testing without these commit shows no problem with negative numbers.
>>
>> Fixes: 80765597bc58 ("tracing: Rewrite filter logic to be simpler and faster")
>> Signed-off-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
>> ---
>> kernel/trace/trace_events_filter.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
>> index 84a65173b1e9..2ba449292561 100644
>> --- a/kernel/trace/trace_events_filter.c
>> +++ b/kernel/trace/trace_events_filter.c
>> @@ -1299,7 +1299,7 @@ static int parse_pred(const char *str, void *data,
>> /* go past the last quote */
>> i++;
>>
>> - } else if (isdigit(str[i])) {
>> + } else if (isdigit(str[i]) || str[i] == '-') {
>>
>> /* Make sure the field is not a string */
>> if (is_string_field(field)) {
>> @@ -1312,6 +1312,9 @@ static int parse_pred(const char *str, void *data,
>> goto err_free;
>> }
>>
>> + if (str[i] == '-')
>> + i++;
>> +
>> /* We allow 0xDEADBEEF */
>> while (isalnum(str[i]))
>> i++;
>
--
Best regards, Tikhomirov Pavel
Software Developer, Virtuozzo.
next prev parent reply other threads:[~2019-02-28 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 10:25 [PATCH] tracing: Fix event filters and triggers to handle negative numbers Pavel Tikhomirov
2018-08-24 0:48 ` Steven Rostedt
2019-02-28 9:11 ` Pavel Tikhomirov [this message]
2019-02-28 16:19 ` 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=f0929165-bc75-c13a-7a20-43262ef8a496@virtuozzo.com \
--to=ptikhomirov@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=viro@ZenIV.linux.org.uk \
/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