On Monday, July 06, 2020 15:07 CEST, Greg Kroah-Hartman wrote: > Just test for memory allocation failure and handle it properly, it isn't > hard to do. > > 128 bytes on the stack can be a problem, don't get in the habit of doing > so please.
Thank you for the clarification. The next version of my patch shall use kstrdup() instead of copying to the stack.
