From: Jarod Wilson <jwilson@redhat.com>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: fw-ohci: plug dma memory leak in AR handler
Date: Wed, 26 Mar 2008 17:37:30 -0400 [thread overview]
Message-ID: <200803261737.30717.jwilson@redhat.com> (raw)
In-Reply-To: <200803251647.16227.jwilson@redhat.com>
On Tuesday 25 March 2008 04:47:16 pm Jarod Wilson wrote:
> There's a nasty memory leak in firewire-ohci's ar_context_tasklet(), in
> that we're not freeing up some of the memory we use for each ar_buffer, due
> to a moving pointer. The problem has been there for a while, but didn't
> start to be noticed until we were doing a coherent allocation for the
> ar_buffer -- meaning we have a smaller pool of memory to work with now, so
> the problem crops up sooner. The manifestation of this comes after doing a
> bunch of I/O to a firewire disk, which eventually stalls, and this starts
> spewing to the console:
>
> PCI-DMA: Out of IOMMU space for 53248 bytes at device 0000:04:09.0
>
> The device there is one of my FireWire controllers trying to do I/O. The
> host is a fairly new rev. opteron.
>
> Just need to make sure we're freeing the correct memory range is pass
> through ar_context_tasklet to fix it. Probably something we ought to sneak
> into 2.6.25 if its still doable...
So as it turns out, while this is indeed a leak that needs to be plugged, it
does NOT remedy the 'out of iommu space' issue, it just delays it a while
longer. Still working on tracing the root cause of the memory exhaustion.
--
Jarod Wilson
jwilson@redhat.com
next prev parent reply other threads:[~2008-03-26 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 20:47 [PATCH] firewire: fw-ohci: plug dma memory leak in AR handler Jarod Wilson
2008-03-25 22:29 ` Stefan Richter
2008-03-26 7:09 ` Stefan Richter
2008-03-26 13:09 ` Jarod Wilson
2008-03-26 23:50 ` Stefan Richter
2008-03-27 7:56 ` Stefan Richter
2008-03-26 21:37 ` Jarod Wilson [this message]
2008-03-27 0:12 ` Stefan Richter
2008-03-27 2:17 ` Jarod Wilson
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=200803261737.30717.jwilson@redhat.com \
--to=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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