On Mon, 3 Jun 2024 at 15:18, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > The logic behind __string() and __assign_str() will always add a NUL > character. Ok. But then you still end up with the issue that now the profiles are different, and you have a 8-byte pointer to dynamically allocated memory instead of just the simpler comm[TASK_COMM_LEN]. Is that actually a good idea for tracing? We're trying to fix the core code to be cleaner for places that may actually *care* (like 'ps'). Would we really want to touch this part of tracing? Linus