Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-15 Thread Du, Changbin
On Tue, Jan 09, 2018 at 11:10:22PM -0500, Steven Rostedt wrote: > On Wed, 10 Jan 2018 11:02:06 +0800 > "Du, Changbin" wrote: > > > On Tue, Jan 09, 2018 at 06:02:58PM -0500, Steven Rostedt wrote: > > > On Tue, 9 Jan 2018 17:55:47 +0800 > > > changbin...@intel.com wrote: >

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-15 Thread Du, Changbin
On Tue, Jan 09, 2018 at 11:10:22PM -0500, Steven Rostedt wrote: > On Wed, 10 Jan 2018 11:02:06 +0800 > "Du, Changbin" wrote: > > > On Tue, Jan 09, 2018 at 06:02:58PM -0500, Steven Rostedt wrote: > > > On Tue, 9 Jan 2018 17:55:47 +0800 > > > changbin...@intel.com wrote: > > > > > > > From:

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread Steven Rostedt
On Wed, 10 Jan 2018 11:02:06 +0800 "Du, Changbin" wrote: > On Tue, Jan 09, 2018 at 06:02:58PM -0500, Steven Rostedt wrote: > > On Tue, 9 Jan 2018 17:55:47 +0800 > > changbin...@intel.com wrote: > > > > > From: Changbin Du > > > > > > The parser

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread Steven Rostedt
On Wed, 10 Jan 2018 11:02:06 +0800 "Du, Changbin" wrote: > On Tue, Jan 09, 2018 at 06:02:58PM -0500, Steven Rostedt wrote: > > On Tue, 9 Jan 2018 17:55:47 +0800 > > changbin...@intel.com wrote: > > > > > From: Changbin Du > > > > > > The parser parse every string into parser.buffer. And

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread Du, Changbin
On Tue, Jan 09, 2018 at 06:02:58PM -0500, Steven Rostedt wrote: > On Tue, 9 Jan 2018 17:55:47 +0800 > changbin...@intel.com wrote: > > > From: Changbin Du > > > > The parser parse every string into parser.buffer. And some of the callers > > assume that parser.buffer

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread Du, Changbin
On Tue, Jan 09, 2018 at 06:02:58PM -0500, Steven Rostedt wrote: > On Tue, 9 Jan 2018 17:55:47 +0800 > changbin...@intel.com wrote: > > > From: Changbin Du > > > > The parser parse every string into parser.buffer. And some of the callers > > assume that parser.buffer contains a C string. So it

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread Steven Rostedt
On Tue, 9 Jan 2018 17:55:47 +0800 changbin...@intel.com wrote: > From: Changbin Du > > The parser parse every string into parser.buffer. And some of the callers > assume that parser.buffer contains a C string. So it is dangerous that the > parser returns a unterminated

Re: [PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread Steven Rostedt
On Tue, 9 Jan 2018 17:55:47 +0800 changbin...@intel.com wrote: > From: Changbin Du > > The parser parse every string into parser.buffer. And some of the callers > assume that parser.buffer contains a C string. So it is dangerous that the > parser returns a unterminated string. The userspace

[PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread changbin . du
From: Changbin Du The parser parse every string into parser.buffer. And some of the callers assume that parser.buffer contains a C string. So it is dangerous that the parser returns a unterminated string. The userspace can leverage this to attack the kernel.

[PATCH 2/3] tracing: make sure the parsed string always terminates with '\0'

2018-01-09 Thread changbin . du
From: Changbin Du The parser parse every string into parser.buffer. And some of the callers assume that parser.buffer contains a C string. So it is dangerous that the parser returns a unterminated string. The userspace can leverage this to attack the kernel. Signed-off-by: Changbin Du Cc: