Re: [PATCH net-next] net: FIB tracepoints

From: David Ahern <redacted>
Date: Thu, 27 Aug 2015 22:27:38 -0700

ie., it does matter. src was declared a u32 and trying to pass &src to
the printk fails. Been down this road a lot.

It's not printk that's failing, it's the tracing library in userspace
that's being stupid about this.

That's where the "FAILED TO PARSE" thing comes from.

This event parsing code is imposing restrictions that do not exist in
the kernel printk.  And in fact I can't think of a justification for
them, why should this code even care as long as the thing is at least
4 bytes.