Re: [for-next][PATCH 09/24] seq_buf: Make seq_buf_puts() null-terminate the buffer

Steven Rostedt writes: > On Fri, 21 Dec 2018 13:00:21 -0500 > Steven Rostedt wrote: > > >> > Can result in: >> > >> > Message is fooªªªªªsecret >> >> Sending this via quilt, and that we have non UTF8 characters causes >> LKML to blow up. >> >> There's a couple more patches with this

Re: [for-next][PATCH 09/24] seq_buf: Make seq_buf_puts() null-terminate the buffer

On Fri, 21 Dec 2018 13:00:21 -0500 Steven Rostedt wrote: > > Can result in: > > > > Message is fooªªªªªsecret > > Sending this via quilt, and that we have non UTF8 characters causes > LKML to blow up. > > There's a couple more patches with this issue. I'm going to fix up the > change

Re: [for-next][PATCH 09/24] seq_buf: Make seq_buf_puts() null-terminate the buffer

On Fri, 21 Dec 2018 12:56:27 -0500 Steven Rostedt wrote: > From: Michael Ellerman > > Currently seq_buf_puts() will happily create a non null-terminated > string for you in the buffer. This is particularly dangerous if the > buffer is on the stack. > > For example: > > char buf[8]; > char