From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Konrad Rzeszutek Wilk
<konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Sibren Vasse <sibren-DLwv2wemLo05ZU0pBKPMFg@public.gmane.org>,
michel-otUistvHUpPR7s880joybQ@public.gmane.org,
freedesktop-DLwv2wemLo05ZU0pBKPMFg@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] swiotlb: clear io_tlb_start and io_tlb_end in swiotlb_exit
Date: Mon, 14 Jan 2019 21:33:23 +0100 [thread overview]
Message-ID: <20190114203323.GA11412@lst.de> (raw)
In-Reply-To: <20190114202513.GG32038-he5eyhs8q0BAdwtm4QZOy9BPR1lH4CV8@public.gmane.org>
On Mon, Jan 14, 2019 at 03:25:13PM -0500, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 14, 2019 at 09:14:08PM +0100, Christoph Hellwig wrote:
> > Otherwise is_swiotlb_buffer will return false positives when
> > we first initialize a swiotlb buffer, but then free it because
> > we have an IOMMU available.
> >
> > Fixes: 55897af63091 ("dma-direct: merge swiotlb_dma_ops into the dma_direct code")
> > Reported-by: Sibren Vasse <sibren-DLwv2wemLo05ZU0pBKPMFg@public.gmane.org>
> > Signed-off-by: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
> > Tested-by: Sibren Vasse <sibren-DLwv2wemLo05ZU0pBKPMFg@public.gmane.org>
>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Do you want to send this to Linus, or do you want me to pick it up
through the dma-mapping tree?
next prev parent reply other threads:[~2019-01-14 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 20:14 [PATCH] swiotlb: clear io_tlb_start and io_tlb_end in swiotlb_exit Christoph Hellwig
[not found] ` <20190114201408.12270-1-hch-jcswGhMUV9g@public.gmane.org>
2019-01-14 20:25 ` Konrad Rzeszutek Wilk
[not found] ` <20190114202513.GG32038-he5eyhs8q0BAdwtm4QZOy9BPR1lH4CV8@public.gmane.org>
2019-01-14 20:33 ` Christoph Hellwig [this message]
[not found] ` <20190114203323.GA11412-jcswGhMUV9g@public.gmane.org>
2019-01-16 14:57 ` Konrad Rzeszutek Wilk
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=20190114203323.GA11412@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=freedesktop-DLwv2wemLo05ZU0pBKPMFg@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=michel-otUistvHUpPR7s880joybQ@public.gmane.org \
--cc=sibren-DLwv2wemLo05ZU0pBKPMFg@public.gmane.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