From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Jin <joe.jin@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
John Sobecki <john.sobecki@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
ASHISH_B_SRIVASTAVA <ashish.b.srivastava@oracle.com>,
stable@vger.kernel.org
Subject: Re: [PATCH UPSTREAM] xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent
Date: Thu, 17 May 2018 21:10:03 +0200 [thread overview]
Message-ID: <20180517191003.GD504@kroah.com> (raw)
In-Reply-To: <25d8a709-9f2f-fe09-f66c-2a0704ddbbb0@oracle.com>
On Thu, May 17, 2018 at 11:45:57AM -0700, Joe Jin wrote:
> When run raidconfig from Dom0 we found that the Xen DMA heap is reduced,
> but Dom Heap is increased by the same size. Tracing raidconfig we found
> that the related ioctl() in megaraid_sas will call dma_alloc_coherent()
> to apply memory. If the memory allocated by Dom0 is not in the DMA area,
> it will exchange memory with Xen to meet the requiment. Later drivers
> call dma_free_coherent() to free the memory, on xen_swiotlb_free_coherent()
> the check condition (dev_addr + size - 1 <= dma_mask) is always false,
> it prevents calling xen_destroy_contiguous_region() to return the memory
> to the Xen DMA heap.
>
> This issue introduced by commit 6810df88dcfc2 "xen-swiotlb: When doing
> coherent alloc/dealloc check before swizzling the MFNs.".
>
> Signed-off-by: Joe Jin <joe.jin@oracle.com>
> Tested-by: John Sobecki <john.sobecki@oracle.com>
> Reviewed-by: Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/xen/swiotlb-xen.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
What does "PATCH UPSTREAM" mean?
confused,
greg k-h
next prev parent reply other threads:[~2018-05-17 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 18:45 [PATCH UPSTREAM] xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent Joe Jin
2018-05-17 19:10 ` Greg KH [this message]
2018-05-17 19:32 ` Joe Jin
2018-05-17 19:32 ` Joe Jin
2018-05-17 19:10 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-05-17 18:45 Joe Jin
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=20180517191003.GD504@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ashish.b.srivastava@oracle.com \
--cc=joe.jin@oracle.com \
--cc=john.sobecki@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.