From: Joerg Roedel <joerg.roedel@amd.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, jeff@garzik.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [NET-NEXT PATCH] ixgbe: fix dma mapping unbalance
Date: Fri, 12 Dec 2008 12:31:47 +0100 [thread overview]
Message-ID: <20081212113147.GE30292@amd.com> (raw)
In-Reply-To: <20081212095104.4380.49487.stgit@lost.foo-projects.org>
Nice. I discoverd a couple more bugs in this driver while testing my
IOMMU code.
One bug can only be found with an hardware IOMMU. This seems to be a
use-after-free bug, at least I see IO_PAGE_FAULTS from the IOMMU
originating from this card. Maybe you can change the VT-d code so that
you can debug this issue.
I didn't found the time yet to do a v2 of my DMA-API debugging patches.
But I hope can will the time for this next week. Then you have something
in hand to debug the driver even further :)
Joerg
On Fri, Dec 12, 2008 at 01:51:05AM -0800, Jeff Kirsher wrote:
> From: Jesse Brandeburg <jesse.brandeburg@intel.com>
>
> This issue was initially reported by Joerg Roedel <joerg.roedel@amd.com>
> It appears that ixgbe has had a long standing bug where it was
> unmapping a different size than it had mapped.
--
| AMD Saxony Limited Liability Company & Co. KG
Operating | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
System | Register Court Dresden: HRA 4896
Research | General Partner authorized to represent:
Center | AMD Saxony LLC (Wilmington, Delaware, US)
| General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-12-12 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 9:51 [NET-NEXT PATCH] ixgbe: fix dma mapping unbalance Jeff Kirsher
2008-12-12 11:31 ` Joerg Roedel [this message]
2008-12-15 9:01 ` David Miller
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=20081212113147.GE30292@amd.com \
--to=joerg.roedel@amd.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).