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] [day] [month] [year] [list]

Message-ID: <486284CE.1000003@cs.wisc.edu>
Date:	Wed, 25 Jun 2008 12:47:58 -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:
> On Wed, Jun 25, 2008 at 10:24 PM, Mike Christie <michaelc@...wisc.edu> wrote:
> 
>>>  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?
> 
> iscsid tried to reconnect but the target died, I think.
> 
>>>  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?
> 
> It was an unmodififed 2.6.25.6 kernel, and open-iscsi version 2.0-869.2
> 
>>> 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.
> 
> Yep, but is there any way to close gracefully and avoid the kernel dump?
> 

What do you mean close gracefully? If you are doing IO to the disk you 
can wait for the host to reconnect and execute the IO. If you are going 
to wait for as long as it takes (or for whatever you have setup in the 
host (see the iscsi documentation/README on open-iscsi.org about the 
replacement_timeout)), and you do not want to see the dump then you can 
do what the dump says and do this I think:

echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

If you want to just disable the message I guess you can do that. But I 
do not think we should even get that far. We should not be firing the 
scsi eh in this case in the first place. I think that might be a bug. I 
attached a patch which will give us more infomation. You can just send 
that output to the iscsi list.


View attachment "debug.patch" of type "text/x-patch" (385 bytes)