Bug 162706

Summary:	iscsi_sfnet driver uses bounce buffers when it does not need to on ia64
Product:	Red Hat Enterprise Linux 3	Reporter:	Mike Christie <mchristi>
Component:	kernel	Assignee:	Mike Christie <mchristi>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	coughlan, davidw, petrides, rkenna
Target Milestone:	---
Target Release:	---
Hardware:	ia64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 18:58:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Christie 2005-07-07 21:18:04 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
The iscsi_sfnet driver does not handle high mem becuase its kmap code is broken (it does a loop with multiple kmap without kunmapping). There is no HW limitation like with some real HW cards. For ia64 though, high mem is set but the kernel memory is mapped. Since the driver does not support high mem only becuase it needs to touch the buffers and to do so it will need to use kmap if the mem is not mapped for ia64 we incorrectly tell the block and scsi layer we need bounce buffers.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. setup iscsi on ia64
2. run IO to iscsi devices and see bounce buffers being used
3.
  

Expected Results:  iscsi driver should not have used bounce buffers

Additional info:

Comment 1 RHEL Program Management 2007-10-19 18:58:37 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.