Re: tcm_fc crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jun,

On Tue, 2014-04-15 at 09:15 -0700, Jun Wu wrote:
> Hello,
> 
> We are working on a cluster file system using fcoe vn2vn. Multiple
> initiators can see the same set of target hard drives exported by
> targetcli tcm_fc. When the initiators run IO to these target hard
> drives at the same time, target system crashes no matter using iblock
> backstore or pscsi backstore. See the following dump.
> 
> crash> bt
> PID: 318    TASK: ffff880c1a05aee0  CPU: 5   COMMAND: "kworker/5:1"
>  #0 [ffff880c1a895a48] machine_kexec at ffffffff810485e2
>  #1 [ffff880c1a895a98] crash_kexec at ffffffff810d09d3
>  #2 [ffff880c1a895b60] oops_end at ffffffff816f0c98
>  #3 [ffff880c1a895b88] die at ffffffff8101616b
>  #4 [ffff880c1a895bb8] do_trap at ffffffff816f04b0
>  #5 [ffff880c1a895c08] do_invalid_op at ffffffff810134a8
>  #6 [ffff880c1a895cb0] invalid_op at ffffffff816f9c1e
>     [exception RIP: ft_queue_data_in+1386]
>     RIP: ffffffffa0641eda  RSP: ffff880c1a895d68  RFLAGS: 00010246
>     RAX: 0000000000001000  RBX: ffff880c17a6dc10  RCX: 0000000000000002
>     RDX: 0000000000000000  RSI: ffff880c1afa36d8  RDI: 0000000000000000
>     RBP: ffff880c1a895df8   R8: ffff880c1667e45c   R9: dfcf2970a166dd90
>     R10: dfcf2970a166dd90  R11: 0000000000000000  R12: ffff880c17a6dc10
>     R13: ffff880c3fc33e00  R14: 0000000000001000  R15: 0000000000000140
>     ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
>  #7 [ffff880c1a895d60] ft_queue_data_in at ffffffffa06419c7 [tcm_fc]
>  #8 [ffff880c1a895e00] target_complete_ok_work at ffffffffa04ded21
> [target_core_
> 
>                             mod]
>  #9 [ffff880c1a895e28] process_one_work at ffffffff8107d0ec
> #10 [ffff880c1a895e70] worker_thread at ffffffff8107dd3c
> #11 [ffff880c1a895ed0] kthread at ffffffff810848d0
> #12 [ffff880c1a895f50] ret_from_fork at ffffffff816f836c
> 
> Is there any way to avoid this problem?

Can you be a bit more specific on the setup..?  Eg: kernel version on
the target, NICs, backstores, etcs.

Also, it might be useful if you can run the RIP (ft_queue_data_in+1386)
through gdb with your kernel source to see where the bug is actually
pointing.

(Also, CC'ing some of the Intel FCoE folks)

--nab

--
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




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux