Re: [PATCH] tracing: Fix event filters and triggers to handle negative numbers

On Thu, 28 Feb 2019 09:11:37 + Pavel Tikhomirov wrote: > 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 wrote: > > > >> Then tracing syscall exit event it is extremely useful to filter exit > >

Re: [PATCH] tracing: Fix event filters and triggers to handle negative numbers

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 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

Re: [PATCH] tracing: Fix event filters and triggers to handle negative numbers

On Thu, 23 Aug 2018 13:25:34 +0300 Pavel Tikhomirov 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" > fil

[PATCH] tracing: Fix event filters and triggers to handle negative numbers

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_rea