All of lore.kernel.org
 help / color / mirror / Atom feed
From: "N.C.Krishna Murthy" <krmurthy@cisco.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: SCSI -DEVEL <linux-scsi@vger.kernel.org>, davmyers@cisco.com
Subject: Re:Request for review of Linux iSCSI driver version 4.0.0.1
Date: Thu, 11 Dec 2003 21:17:46 +0530	[thread overview]
Message-ID: <200312112117.46216.krmurthy@cisco.com> (raw)

Hi,
	One of your comments was
"having multiple kmap() in the same process at the same time can deadlock(),
you redesign iscsi_xmit_task/iscsi_xmit_data/iscsi_recv_data not to do that.
for the tx path use ->sendpage to avoid a data copy and kmapping altogether".

I did try using sendpage in iscsi_xmit_data. 
Whenever the scatterlist->length was 4096 sendpage did succeed.
When it was 8192 I did see a panic 
------------------------------------------------------------------------------------------
Unable to handle kernel NULL pointer dereference
 at virtual address 00000004
Dec 11 08:55:22 linux-3 kernel:  printing eip:
Dec 11 08:55:22 linux-3 kernel: c03e24ec
Dec 11 08:55:22 linux-3 kernel: *pde = 00000000
Dec 11 08:55:22 linux-3 kernel: Oops: 0002 [#1]
Dec 11 08:55:22 linux-3 kernel: CPU:    0
Dec 11 08:55:22 linux-3 kernel: EIP:    0060:[__func__.4+49981/364885]    Not 
ta
inted
Dec 11 08:55:22 linux-3 kernel: EIP:    0060:[<c03e24ec>]    Not tainted
Dec 11 08:55:22 linux-3 kernel: EFLAGS: 00010287
Dec 11 08:55:22 linux-3 kernel: EIP is at do_tcp_sendpages+0x62e/0xb8a
------------------------------------------------------------------------------------------
Has this been seen earlier? 

Thanx
N.C.Krishna Murthy

             reply	other threads:[~2003-12-11 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 15:47 N.C.Krishna Murthy [this message]
2003-12-12 12:48 ` Request for review of Linux iSCSI driver version 4.0.0.1 Matthew Wilcox
2003-12-12 15:29   ` N.C.Krishna Murthy
2003-12-13  2:46   ` Andre Hedrick

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=200312112117.46216.krmurthy@cisco.com \
    --to=krmurthy@cisco.com \
    --cc=davmyers@cisco.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    /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.