linux-kernel - Re: Kernel Crash when using the open-iscsi initiator on 2.6.25.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Jun 2008 11:54:41 -0500
From:	Mike Christie <michaelc@...wisc.edu>
To:	Ashutosh Naik <ashutosh.naik@...il.com>
CC:	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	open-iscsi@...glegroups.com
Subject: Re: Kernel Crash when using the open-iscsi initiator on 2.6.25.6

Ashutosh Naik wrote:
> Please find the kernel log attached. I was using the open-iscsi
> initiator on kernel 2.6.25.6 with a chelsio iSCSI target and the crash
> happened on the initiator machine.
> 
>  connection5:0: ping timeout of 5 secs expired, last rx 4309640121,
> last ping 4309645121, now 4309650121
>  connection5:0: detected conn error (1011)

This happens when we cannot reach the target for the noop timout and 
interval seconds, which can happen if a cable is unplugged or the 
network is not reach able or is dropping packets.

>  connection5:0: ping timeout of 5 secs expired, last rx 4309652882,
> last ping 4309657882, now 4309662882

However, once it happens we should not report it again like is done 
here. There is something weird there. Do you have the iscsid output? 
Between these two reports of pings timing out is there any messages from 
iscsid about reconnecting?

>  connection5:0: detected conn error (1011)
>  connection5:0: detected conn error (1011)
>  session5: host reset succeeded

And we should not get here. The iscsi driver's scsi command timeout 
handler should prevent the command from firing the scsi eh, because in 
this case we think it is a transport problem.

What version of the iscsi tools are you using? Are they from a distro or 
open-iscsi.org?

Are you running with the iscsi kernel modules from 2.6.25.6, or are you 
using the iscsi modules from the open-iscsi.org website that come with 
the tarball?

Is the kernel a unmodified 2.6.25.6 or does it have some distro patches 
or patches that you have created?

> INFO: task fdisk:5226 blocked for more than 120 seconds.

I think you get this message and what follows, is a result of the above 
problem. While the iscsi initiator is trying to reconnect, IO is queued 
by the scsi layer so fdisk is going to be waiting around until we 
recover or give up.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/