public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH] x86_84 pci_map_sg fix for 2.6.0-test7
Date: Sat, 11 Oct 2003 01:11:37 +0200	[thread overview]
Message-ID: <20031010231137.GA28985@wotan.suse.de> (raw)
In-Reply-To: <200310101426.33773.pbadari@us.ibm.com>

On Fri, Oct 10, 2003 at 02:26:33PM -0700, Badari Pulavarty wrote:
> Hi,
> 
> Here is the patch to fix few minor issues with pci_map_sg() and pci_map_cont()
> for x86_64. I ran into these asserts while testing with qlogic fc driver.

Sounds like the driver is buggy.

> 
> The patch fixes following:
> 
> 1) pci_map_sg() coalsces "sg" entries without modifying command's
> "use_sg" value. It sets the "sg" entries length to "0" to indicate that
> these entires are coalsced. If the command gets retried, the pci_map_sg() 
> code trips on the assert that all entries length should be > 0.

As I explained for your last patch this change is wrong. Remapping
an already mapped sg is not possible - it leaks IOMMU space and 
cause eventually system failure when the aperture fills up.

You have to somehow handle this in the caller, the pci-dma
layer cannot do it. Eeither free the modified sg and retry with the original 
one or better just don't remap it and use the already mapped one) 

I will add an BUG for passing sgs with dma_address != NULL to 
pci_map_sg(). This should catch such abuses early.

> 
> 2) __pci_map_cont() incorrectly assumes that "start" is always 0, so it
> trips on few asserts.

That's the same high level bug I think.  

-Andi


  reply	other threads:[~2003-10-10 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 21:26 [PATCH] x86_84 pci_map_sg fix for 2.6.0-test7 Badari Pulavarty
2003-10-10 23:11 ` Andi Kleen [this message]
2003-10-10 23:37   ` Badari Pulavarty

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=20031010231137.GA28985@wotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox