Please don't drop CCs.
Qi, Yanling [EMAIL PROTECTED] wrote:
Qi, Yanling [EMAIL PROTECTED] wrote:
@@ -2571,6 +2572,13 @@ sg_page_malloc(int rqSz, int lowDma, int
resp = (char *) __get_free_pages(page_mask, order);
/* try half */
resSz = a_size;
}
PROTECTED];
[EMAIL PROTECTED]
Subject: Re: SG_IO with 4k buffer size to iscsi sg device causes Bad
page panic
Qi, Yanling [EMAIL PROTECTED] wrote:
@@ -2571,6 +2572,13 @@ sg_page_malloc(int rqSz, int lowDma, int
resp = (char *) __get_free_pages(page_mask, order);
/* try half
-Original Message-
From: Mike Christie [mailto:[EMAIL PROTECTED]
Qi, Yanling wrote:
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
Qi, Yanling [EMAIL PROTECTED] wrote:
@@ -2571,6 +2572,13 @@ sg_page_malloc(int rqSz, int lowDma, int
resp = (char *) __get_free_pages(page_mask, order);
/* try half */
resSz = a_size;
}
+ tmppage = virt_to_page(resp);
+ for( m = PAGE_SIZE; m
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
Bad page panic first. I did a patch to the sg driver to workaround the
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
