From: Zubin Mithra <zsm@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, groeck@chromium.org,
christian.koenig@amd.com, michel.daenzer@amd.com,
Jerry.Zhang@amd.com, ray.huang@amd.com,
alexander.deucher@amd.com
Subject: Re: ac1e516d5a4c ("drm/ttm: fix start page for huge page check in ttm_put_pages()")
Date: Wed, 15 Jan 2020 22:44:40 -0800 [thread overview]
Message-ID: <20200116064439.GA62849@google.com> (raw)
In-Reply-To: <20200116062954.GA1172661@kroah.com>
On Thu, Jan 16, 2020 at 07:29:54AM +0100, Greg KH wrote:
> On Wed, Jan 15, 2020 at 07:55:02PM -0800, Zubin Mithra wrote:
> > Hello,
> >
> > The patch :
> > a66477b0efe5 ("drm/ttm: fix out-of-bounds read in ttm_put_pages() v2")
> >
> > has been applied to linux-4.19.y. However, 2 follow-up fixes have not been applied.
>
> How did you figure out that they were "follow-up" fixes?
CVE-2019-19927 references commits a66477b0efe5, ac1e516d5a4c and
453393369dc9.
The patch author(Christian König) confirmed that if the patches were being backported,
then all three of them need to be.
Thanks,
- Zubin
>
> >
> > Could the following two fixes be applied to linux-4.19.y? These commits are present
> > in linux-5.4.y. These patches do not have to be applied to linux-4.14.y.
> >
> > ac1e516d5a4c ("drm/ttm: fix start page for huge page check in ttm_put_pages()")
> > 453393369dc9 ("drm/ttm: fix incrementing the page pointer for huge pages")
>
> Both now queued up, thanks for letting me know.
>
> greg k-h
prev parent reply other threads:[~2020-01-16 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 3:55 ac1e516d5a4c ("drm/ttm: fix start page for huge page check in ttm_put_pages()") Zubin Mithra
2020-01-16 6:29 ` Greg KH
2020-01-16 6:44 ` Zubin Mithra [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=20200116064439.GA62849@google.com \
--to=zsm@chromium.org \
--cc=Jerry.Zhang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=michel.daenzer@amd.com \
--cc=ray.huang@amd.com \
--cc=stable@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 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.