All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Olaf Kirch <olaf.kirch@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: iSCSI fun in 2.6.21-rc6
Date: Wed, 18 Apr 2007 17:19:31 -0400	[thread overview]
Message-ID: <46268B63.8000201@cs.wisc.edu> (raw)
In-Reply-To: <200704182102.42805.olaf.kirch@oracle.com>

Olaf Kirch wrote:
> On Wednesday 18 April 2007 17:38, Mike Christie wrote:
>> Could you send the trace? It is weird that we would get a storm of data
>> out commands for a IO that was only 4096 bytes (assuming part of the log
>> did not get cut off and the above line is the last one).
> 
> It turns out max_xmit_dlength was 0, hence it kept looping
> forever in an attempt to chop a 4096 byte payload into an
> infinite number of 0-sized pieces :-)
> 
> It turns out there was an old iscsid in $PATH that spoke an
> older netlink dialect, so any parameters set by iscsid never
> reached the iscsi transport, and the connection essentially went
> unconfigured.
> 
> So, how about some consistency checks prior to connecting?
> I'll submit a patch if you'd be willing to consider it.
> 

Ok send it. I added checks in userspace to make sure we got valid input
from users. This is in the svn code. In the kernel I only added minimal
checking for invalid burst length settings we could get from some
targets iscsi_conn_start. In the kernel I would add on to them.

      reply	other threads:[~2007-04-18 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18 14:22 iSCSI fun in 2.6.21-rc6 Olaf Kirch
2007-04-18 15:38 ` Mike Christie
2007-04-18 17:57   ` Mike Christie
2007-04-18 19:02   ` Olaf Kirch
2007-04-18 21:19     ` Mike Christie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46268B63.8000201@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olaf.kirch@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.