nvme-tcp: kernel NULL pointer dereference, address: 0000000000000034

[Chaitanya Kulkarni]

>> Never seen anyone try to use poll queues with nvme tcp before. It doesn't look
>> like that would work for a connect command since there's no bdev at this point,
>> and polling needs a bdev.
> Thanks for pointing me in the right direction.
> I wrote a test program that exercises all the different options available.
> The crash went away once I removed "nr-poll-queues=4".
> But this begs the question: should a user-space program be given the ability
> to crash the kernel by simply providing the wrong (or weird) arguments?
>
>

Can you please submit a blktests for the nvme category ?
that way it will get exercised by everyone on the mailing list ?

-ck