On Monday, April 9, 2018 at 9:38:51 PM UTC-7, tej parkash wrote:
>
> Hi All, 
>
> On RHEL 7.4 once we have seen that kernel panic while doing iser 
> disconnect. Following is the stack observed
>
> [276413.836283] RIP: 0010:[<ffffffff812819c6>]  [<ffffffff812819c6>] 
> sysfs_find_dirent+0x16/0xf0
> [276413.836319] RSP: 0018:ffff88045620b908  EFLAGS: 00010246
> [276413.836340] RAX: ffff880468d2cf10 RBX: 0000000000000000 RCX: 
> ffff88045620bfd8
> [276413.836369] RDX: ffffffff81734e08 RSI: 0000000000000000 RDI: 
> 0000000000000000
> [276413.836397] RBP: ffff88045620b928 R08: 000000000000000a R09: 
> 0000000000000000
> [276413.836425] R10: 00000000002b0f75 R11: ffff88045620b596 R12: 
> 0000000000000000
> [276413.836453] R13: ffffffff81734e08 R14: 0000000000000000 R15: 
> 0000000000000048
> [276413.836481] FS:  00007f5ca250c880(0000) GS:ffff88046f3c0000(0000) 
> knlGS:0000000000000000
> [276413.836514] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [276413.836547] CR2: 0000000000000060 CR3: 000000046dbc1000 CR4: 
> 00000000001407e0
> [276413.836585] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 
> 0000000000000000
> [276413.836617] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 
> 0000000000000400
> [276413.836648] Stack:
> [276413.836660]  0000000000000000 0000000000000000 ffffffff81734e08 
> 0000000000000000
> [276413.836694]  ffff88045620b950 ffffffff81281ad1 ffffffff81ac44e0 
> ffff8804006f0808
> [276413.836737]  ffff8804083990e8 ffff88045620b970 ffffffff812836ed 
> ffff8804006f0818
> [276413.836780] Call Trace:
> [276413.836798]  [<ffffffff81281ad1>] sysfs_get_dirent+0x31/0x70
> [276413.836826]  [<ffffffff812836ed>] sysfs_unmerge_group+0x1d/0x70
> [276413.836852]  [<ffffffff814477f2>] dpm_sysfs_remove+0x22/0x60
> [276413.836877]  [<ffffffff8143ad75>] device_del+0x45/0x210
> [276413.836908]  [<ffffffff8143af5e>] device_unregister+0x1e/0x60
> [276413.836958]  [<ffffffffc082b526>] iscsi_destroy_endpoint+0x26/0x30 
> [scsi_transport_iscsi]
> [276413.836996]  [<ffffffffc084792a>] iscsi_iser_ep_disconnect+0xca/0x100 
> [ib_iser]
> [276413.837033]  [<ffffffffc082effa>] 
> iscsi_if_ep_disconnect.isra.14+0x5a/0x70 [scsi_transport_iscsi]
> [276413.837085]  [<ffffffffc08302fb>] iscsi_if_recv_msg+0x113b/0x14a0 
> [scsi_transport_iscsi]
> [276413.837140]  [<ffffffff811e20a8>] ? 
> __kmalloc_node_track_caller+0x58/0x290
> [276413.837188]  [<ffffffffc08306ee>] iscsi_if_rx+0x8e/0x1f0 
> [scsi_transport_iscsi]
> [276413.837228]  [<ffffffff815bd012>] netlink_unicast+0xf2/0x1b0
> [276413.838760]  [<ffffffff815bd3ef>] netlink_sendmsg+0x31f/0x6a0
>
>
> Any Idea?. I have complete vmcore file with me. Attached for now 
> only vmcore-dmesg.txt. let me know if any other data is required. 
>
> Thanks
> Tej
>

This list is for open-iscsi (iscsi initiator) software discussion, and you 
seem to be having issues with the kernel target drivers.

Try the target-devel kernel list. 

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at https://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to