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>,
"DONGLI.ZHANG" <dongli.zhang@oracle.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] xen-swiotlb: use actually allocated size on check physical contiguous
Date: Tue, 4 Sep 2018 21:13:30 +0200 [thread overview]
Message-ID: <20180904191330.GA16532@kroah.com> (raw)
In-Reply-To: <d578b69a-848b-2c86-175a-1b1933d82a36@oracle.com>
On Tue, Sep 04, 2018 at 11:16:58AM -0700, Joe Jin wrote:
> xen_swiotlb_{alloc,free}_coherent() actually allocate/free size by order
> but used the required size to check if address is physical contiguous,
> if first pages are physical contiguous also passed
> range_straddles_page_boundary() check, but others were not it will
> lead kernel panic.
>
> Signed-off-by: Joe Jin <joe.jin@oracle.com>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> ---
> drivers/xen/swiotlb-xen.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2018-09-04 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 18:16 [PATCH] xen-swiotlb: use actually allocated size on check physical contiguous Joe Jin
2018-09-04 19:13 ` Greg KH
2018-09-04 19:13 ` Greg KH [this message]
2018-09-04 23:14 ` [Xen-devel] " Dongli Zhang
2018-09-04 23:36 ` Andrew Cooper
2018-09-04 23:36 ` [Xen-devel] " Andrew Cooper
2018-09-07 22:47 ` Joe Jin
2018-09-07 22:47 ` [Xen-devel] " Joe Jin
2018-09-04 23:14 ` Dongli Zhang
-- strict thread matches above, loose matches on Subject: below --
2018-09-04 18:16 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=20180904191330.GA16532@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dongli.zhang@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.