netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Beregalov <a.beregalov@gmail.com>
To: Maciej Sosnowski <maciej.sosnowski@intel.com>
Cc: dan.j.williams@intel.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] ioatdma: fix "ioatdma frees DMA memory with wrong function"
Date: Tue, 12 May 2009 14:03:25 +0400	[thread overview]
Message-ID: <a4423d670905120303y5dc8760fva244f62460cfd2c8@mail.gmail.com> (raw)
In-Reply-To: <20090423123128.31427.20238.stgit@linux.site>

2009/4/23 Maciej Sosnowski <maciej.sosnowski@intel.com>:
> as reported by Alexander Beregalov <a.beregalov@gmail.com>
>
> ioatdma 0000:00:08.0: DMA-API: device driver frees DMA memory with
> wrong function [device address=0x000000007f76f800] [size=2000 bytes]
> [map
> ped as single] [unmapped as page]
>
> The ioatdma driver was unmapping all regions
> (either allocated as page or single) using unmap_page.
> This patch lets dma driver recognize if unmap_single or unmap_page should be used.
> It introduces two new dma control flags:
> DMA_COMPL_SRC_UNMAP_SINGLE and DMA_COMPL_DEST_UNMAP_SINGLE.
> They should be set to indicate dma driver to do dma-unmapping as single
> (first one for the source, tha latter for the destination).
> If respective flag is not set, the driver assumes dma-unmapping as page.
>
> Signed-off-by: Maciej Sosnowski <maciej.sosnowski@intel.com>
> Acked-by: Dan Williams <dan.j.williams@intel.com>
> Reported-by: Alexander Beregalov <a.beregalov@gmail.com>
> Tested-by: Alexander Beregalov <a.beregalov@gmail.com>
> ---

Will it be sent to Linus ?

      reply	other threads:[~2009-05-12 10:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 12:31 [PATCH] ioatdma: fix "ioatdma frees DMA memory with wrong function" Maciej Sosnowski
2009-05-12 10:03 ` Alexander Beregalov [this message]

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=a4423d670905120303y5dc8760fva244f62460cfd2c8@mail.gmail.com \
    --to=a.beregalov@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.sosnowski@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).