On Wed, May 22, 2024 at 09:32:03PM -0700, Linus Torvalds wrote: > On Wed, 22 May 2024 at 19:38, Yafang Shao <laoar.shao@xxxxxxxxx> wrote: > > > > Indeed, the 16-byte limit is hard-coded in certain BPF code: > > It's worse than that. > > We have code like this: > > memcpy(__entry->comm, t->comm, TASK_COMM_LEN); FYI, I would be happy to convert the tracing events over to dynamic strings. It takes a 4 byte meta data that holds the offset and size of the string, then the string itself (appended at the end of the event buffer) as well as the space. The sched_switch and sched_waking events were created before the dynamic string code was added, hence the hard coded size. I'm not sure what fallout that would have for user space tools, as some tooling does hardcode the parsing of the sched event. But I'm sure I can work to fix those tools. -- Steve
