On 11/26/2013 07:46 AM, Steven Rostedt wrote:
On Fri, 22 Nov 2013 23:18:09 +0100
"Rafael J. Wysocki" wrote:
On Friday, November 22, 2013 10:54:29 AM Shuah Khan wrote:
Tracing infrastructure routine __assign_str doesn't handle null strings.
As a result when an trace event passes in a null stri
On Fri, 22 Nov 2013 23:18:09 +0100
"Rafael J. Wysocki" wrote:
> On Friday, November 22, 2013 10:54:29 AM Shuah Khan wrote:
> > Tracing infrastructure routine __assign_str doesn't handle null strings.
> > As a result when an trace event passes in a null string, kernel panics
> > when skip_spaces()
On Friday, November 22, 2013 10:54:29 AM Shuah Khan wrote:
> Tracing infrastructure routine __assign_str doesn't handle null strings.
> As a result when an trace event passes in a null string, kernel panics
> when skip_spaces() is invoked on the string. The following oops occurred
> when a null wak
Tracing infrastructure routine __assign_str doesn't handle null strings.
As a result when an trace event passes in a null string, kernel panics
when skip_spaces() is invoked on the string. The following oops occurred
when a null wakeup source name is specified.
power_supply_register() calls device
4 matches
Mail list logo