Re: [PATCH v2 1/3] tracing: Change STR_VAR_MAX_LEN

Hi Axel, On Wed, 2020-09-30 at 15:45 -0700, Axel Rasmussen wrote: > I still get the same WARN_ON behavior when trying to use bpftrace. > But, I spent some time today reading through that call path, and at > this point I'm convinced that it's the version of bpftrace I'm using > which is slightly br

Re: [PATCH v2 1/3] tracing: Change STR_VAR_MAX_LEN

I still get the same WARN_ON behavior when trying to use bpftrace. But, I spent some time today reading through that call path, and at this point I'm convinced that it's the version of bpftrace I'm using which is slightly broken, not the kernel in this case. (To be fair, I'm trying to use some unre

[PATCH v2 1/3] tracing: Change STR_VAR_MAX_LEN

32 is too small for this value, and anyway it makes more sense to use MAX_FILTER_STR_VAL, as this is also the value used for variable-length __strings. Signed-off-by: Tom Zanussi --- kernel/trace/trace_synth.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/trace/trace