On Apr 22, 2013, at 9:49 AM, Mark Rustad <mark.d.rustad@xxxxxxxxx> wrote: > Add a check for an aborted sequence, which has a > NULL sequence pointer, to avoid target crashes. > The most relevant messages from the crash (entered > from video capture) include: > > BUG: unable to handle kernel paging request at ffffffffffffffdf > IP: [<ffffffffa02d514c>] fc_seq_send+0x3c/0x150 [libfc] > ... > Call Trace: > [<ffffffffa0443de6>] ft_queue_data_in+0x266/0x560 [tcm_fc] > > Signed-off-by: Mark Rustad <mark.d.rustad@xxxxxxxxx> This is an issue encountered by a user on a setup in one of our labs. It appeared that for some reason that particular setup was suffering from occasional frame loss, which resulted in exchange aborts. Sometimes those exchange aborts resulted in this crash. This patch appears to fix the problem by checking the sequence pointer for null every time through this loop and using the value that was checked for the exchange pointer. -- Mark Rustad, Networking Division, Intel Corporation-- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
