UBI leb_write_unlock NULL pointer Oops (continuation)

[Richard Weinberger]

Am 12.02.2014 16:18, schrieb Wiedemer, Thorsten (Lawo AG):
>> On 11 Feb 2014, Thorsten.Wiedemer at lawo.com wrote:
>>
>>> short update (I was out of office the rest of last week).  I compiled 
>>>  the kernel with the debug flags for debug list and lock alloc.  The 
>>> kernel compiled with gcc-4.8.2 didn't start (no output on serial 
>>>  console and reboot of the system).  I didn't try (yet) to find out 
>>>  what happens at startup.
>>
>> You don't need to enable the 'lock alloc' debugging; Just the 'debug list' as Richard suggested.  One at a time would work and give clues if you 
>> can reproduce it.
> 
> 
> I tested this, compiled with gcc.4-4-4. I had an error one time, but there was no bug report for list handling, only kernel oops:

Are you able to trigger the bug with function tracing enabled?
If so, please add the ftrace_dump_on_oops kernel parameter. Such that we see what happened before oops.

Thanks,
//richard