From: Mike Christie <michaelc@cs.wisc.edu>
To: open-iscsi@googlegroups.com
Cc: netdev@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-iscsi-devel@lists.sourceforge.net, "Qi,
Yanling" <Yanling.Qi@lsi.com>,
dougg@torque.net, James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: SG_IO with >4k buffer size to iscsi sg device causes "Bad page" panic
Date: Tue, 08 May 2007 14:30:16 -0500 [thread overview]
Message-ID: <4640CFC8.9020004@cs.wisc.edu> (raw)
In-Reply-To: <0F08E10B769EAF4EA2C43A573B8CC87FB106C0@NAMAIL3.ad.lsil.com>
Qi, Yanling wrote:
> Hi All,
>
> This panic is related to the interactions between scsi/sg.c, iscsi
> initiator and tcp on the RHEL 2.6.9-42 kernel. But we may also have the
> similar problem with open-iscsi initiator. I will explain why we see the
Yeah, this problem should occur in the upstream open-iscsi iscsi code.
open-iscsi works very similar to linux-scsi where it just sends pages
around with sock->ops-sendpage, and it looks like sg uses
__get_free_pages in RHEL's kernel and upstream it uses alloc_pages so
unless there was a change in those functions or the network layer then
we should have a similar problem.
next prev parent reply other threads:[~2007-05-08 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 18:08 SG_IO with >4k buffer size to iscsi sg device causes "Bad page" panic Qi, Yanling
2007-05-08 18:08 ` Qi, Yanling
2007-05-08 19:30 ` Mike Christie [this message]
2007-05-09 16:13 ` Qi, Yanling
2007-05-09 16:13 ` Qi, Yanling
2007-05-09 23:38 ` Herbert Xu
2007-05-09 23:38 ` Herbert Xu
2007-05-10 18:31 ` Qi, Yanling
2007-05-10 18:31 ` Qi, Yanling
2007-06-08 6:22 ` Herbert Xu
2007-06-08 6:22 ` Herbert Xu
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=4640CFC8.9020004@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=Yanling.Qi@lsi.com \
--cc=dougg@torque.net \
--cc=linux-iscsi-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=open-iscsi@googlegroups.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.