From: Yu Zhao <yuzhao@google.com>
To: Christian Koenig <christian.koenig@amd.com>,
Huang Rui <ray.huang@amd.com>, Junwei Zhang <Jerry.Zhang@amd.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/ttm: properly unmap dma page upon failure
Date: Sat, 6 Jul 2019 11:33:09 -0600 [thread overview]
Message-ID: <20190706173309.GA111051@google.com> (raw)
In-Reply-To: <20190325202250.212801-1-yuzhao@google.com>
On Mon, Mar 25, 2019 at 02:22:50PM -0600, Yu Zhao wrote:
> dma_unmap_page() must be called with exactly the same dma address
> and size returned by dma_map_page(). Otherwise, the function may
> fail.
>
> This is at least the case for debug_dma_unmap_page() and AMD iommu
> unmap_page callback.
Hi, can we please take this fix? Thanks.
prev parent reply other threads:[~2019-07-06 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 20:22 [PATCH] drm/ttm: properly unmap dma page upon failure Yu Zhao
2019-07-06 17:33 ` Yu Zhao [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=20190706173309.GA111051@google.com \
--to=yuzhao@google.com \
--cc=Jerry.Zhang@amd.com \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.huang@amd.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;
as well as URLs for NNTP newsgroup(s).