From: Boaz Harrosh <bharrosh@panasas.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: just.for.lkml@googlemail.com, hancockrwd@gmail.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: sata_sil24 0000:04:00.0: DMA-API: device driver frees DMA sg list with different entry count [map count=13] [unmap count=10]
Date: Thu, 04 Jun 2009 10:15:14 +0300 [thread overview]
Message-ID: <4A277482.5070909@panasas.com> (raw)
In-Reply-To: <20090604153253B.fujita.tomonori@lab.ntt.co.jp>
On 06/04/2009 09:33 AM, FUJITA Tomonori wrote:
> On Thu, 4 Jun 2009 08:12:34 +0200
> Torsten Kaiser <just.for.lkml@googlemail.com> wrote:
>
>> On Thu, Jun 4, 2009 at 2:02 AM, FUJITA Tomonori
>> <fujita.tomonori@lab.ntt.co.jp> wrote:
>>> On Wed, 3 Jun 2009 21:30:32 +0200
>>> Torsten Kaiser <just.for.lkml@googlemail.com> wrote:
>>>> Still happens with 2.6.30-rc8 (see trace at the end of the email)
>>>>
>>>> As orig_n_elem is only used two times in libata-core.c I suspected a
>>>> corruption of the qc->sg, but adding checks for this did not trigger.
>>>> So I looked into lib/dma-debug.c.
>>>> It seems add_dma_entry() does not protect against adding the same
>>>> entry twice.
>>> Do you mean that add_dma_entry() doesn't protect against adding a new
>>> entry identical to the existing entry, right?
>> Yes, as I read the hash bucket code in lib/dma-debug.c a second entry
>> from the same device and the same address will just be added to the
>> list and on unmap it will always return the first entry.
>
> It means that two different DMA operations will be performed against
> the same dma addresss on the same device at the same time. It doesn't
> happen unless there is a bug in a driver, an IOMMU or somewhere, as I
> wrote in the previous mail.
>
What about the draining buffers used by libata. Are they not the same buffer
for all devices for all requests?
>
>>> Then it's not a
>>> dma-debug bug (it might be better for dma-debug to check it though),
>>> that is, such situation should not happen.
>> At least the warning about the wrong unmap count is a bug in the
>> dma-debug, as that is not what happens on my system.
>>
>>> Probably, it's an IOMMU bug
>>> or a driver bug.
>> Could it be just a forgotten unmap?
>> That would leave the old entry in the dma-debug list, but from the
>> driver side it would be valid to map the same place again without
>> corrupting any data transfer to the harddisk.
>
> Yeah, I thought about this possibility. However, you use GART IOMMU,
> right (you can see "PCI-DMA: using GART IOMMU." in a boot message if
> so)? If you use GART IOMMU, unmapped addresses are not reused.
>
>
>> What also would point in this direction, sometime I have seen this in my log:
>> [ 1004.061989] DMA-API: debugging out of memory - disabling
>
> Sounds like there is a leak...
Boaz
next prev parent reply other threads:[~2009-06-04 7:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 19:14 sata_sil24 0000:04:00.0: DMA-API: device driver frees DMA sg list with different entry count [map count=13] [unmap count=10] Torsten Kaiser
2009-05-26 19:14 ` Torsten Kaiser
2009-05-26 23:40 ` Robert Hancock
2009-05-27 2:11 ` Torsten Kaiser
2009-05-27 2:11 ` Torsten Kaiser
2009-06-03 19:30 ` Torsten Kaiser
2009-06-03 19:30 ` Torsten Kaiser
2009-06-03 20:21 ` Kasper Sandberg
2009-06-03 23:33 ` Robert Hancock
2009-06-04 6:00 ` Torsten Kaiser
2009-06-04 6:00 ` Torsten Kaiser
2009-06-04 0:02 ` FUJITA Tomonori
2009-06-04 6:12 ` Torsten Kaiser
2009-06-04 6:12 ` Torsten Kaiser
2009-06-04 6:33 ` FUJITA Tomonori
2009-06-04 7:15 ` Boaz Harrosh [this message]
2009-06-04 7:44 ` FUJITA Tomonori
2009-06-04 7:53 ` Jens Axboe
2009-06-04 18:07 ` Torsten Kaiser
2009-06-04 18:07 ` Torsten Kaiser
2009-06-04 22:43 ` FUJITA Tomonori
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=4A277482.5070909@panasas.com \
--to=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hancockrwd@gmail.com \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.