t; ha scritto:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Il giorno 10 gen 2018, alle ore 05:58, Ming Lei
> >>>>>> ha scritto:
> >>>>>>
> >>>>>> Hi Paolo,
>
a
>>>>>> scritto:
>>>>>>
>>>>>> Hi Paolo,
>>>>>>
>>>>>> Looks this one is introduced in recent merge, and it is triggered
>>>>>> in test of IO vs. removing device on the latest for-next of bl
;>>> ha scritto:
>>>>
>>>>
>>>>
>>>>> Il giorno 10 gen 2018, alle ore 05:58, Ming Lei ha
>>>>> scritto:
>>>>>
>>>>> Hi Paolo,
>>>>>
>>>>> Looks this one is in
gt;>>> Il giorno 10 gen 2018, alle ore 05:58, Ming Lei ha
>>>> scritto:
>>>>
>>>> Hi Paolo,
>>>>
>>>> Looks this one is introduced in recent merge, and it is triggered
>>>> in test of IO vs. removing device on the latest for-
10 gen 2018, alle ore 05:58, Ming Lei ha
> >>> scritto:
> >>>
> >>> Hi Paolo,
> >>>
> >>> Looks this one is introduced in recent merge, and it is triggered
> >>> in test of IO vs. removing device on the latest for-next of block
>
>>> Looks this one is introduced in recent merge, and it is triggered
>>> in test of IO vs. removing device on the latest for-next of block
>>> tree:
>>>
>>> [ 296.151615] BUG: unable to handle kernel NULL pointer dereference at
>>>
;> in test of IO vs. removing device on the latest for-next of block
>> tree:
>>
>> [ 296.151615] BUG: unable to handle kernel NULL pointer dereference at
>> 0436
>> [ 296.152302] IP: percpu_counter_add_batch+0x25/0x9d
>> [ 296.152698] PGD
> Il giorno 10 gen 2018, alle ore 05:58, Ming Lei ha
> scritto:
>
> Hi Paolo,
>
> Looks this one is introduced in recent merge, and it is triggered
> in test of IO vs. removing device on the latest for-next of block
> tree:
>
> [ 296.151615] BUG: unable
Hi Paolo,
Looks this one is introduced in recent merge, and it is triggered
in test of IO vs. removing device on the latest for-next of block
tree:
[ 296.151615] BUG: unable to handle kernel NULL pointer dereference at
0436
[ 296.152302] IP: percpu_counter_add_batch+0x25/0x9d
