From: Greg KH <greg@kroah.com>
To: Rob Clark <robdclark@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
stable <stable@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Kasin Li <donglil@codeaurora.org>,
Jordan Crouse <jcrouse@codeaurora.org>
Subject: Re: [stable] drm/msm: Fix potential buffer overflow issue
Date: Mon, 6 Nov 2017 08:56:35 +0100 [thread overview]
Message-ID: <20171106075635.GA18507@kroah.com> (raw)
In-Reply-To: <CAF6AEGvDRkXyAwgtWM9dKDk5z=pptWycPQENHWOvFAFStrzs8Q@mail.gmail.com>
On Fri, Nov 03, 2017 at 06:54:50PM -0400, Rob Clark wrote:
> On Tue, Oct 31, 2017 at 1:01 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > These commits appear to be needed in all stable branches from 3.12
> > onward:
> >
> > commit 4a630fadbb29d9efaedb525f1a8f7449ad107641
> > Author: Kasin Li <donglil@codeaurora.org>
> > Date: Mon Jun 19 15:36:53 2017 -0600
> >
> > drm/msm: Fix potential buffer overflow issue
> >
> > commit 65e93108891e571f177c202add9288eda9ac4100
> > Author: Dan Carpenter <dan.carpenter@oracle.com>
> > Date: Fri Jun 30 10:59:15 2017 +0300
> >
> > drm/msm: fix an integer overflow test
> >
>
> I guess we do not need to go *all* the way back to 3.12, since drm/msm
> was somewhat ahead of curve on the work to get upstream kernels
> working on various snapdragon devices without needing a pile of other
> patches. Maybe going back one or two LTS's would make sense? I think
> apq8064 was probably the one that was working on upstream kernel the
> earliest without extra patches needed. I can double check when that
> was, I think that puts a reasonable upper bound on how far back to
> backport.
>
> Let me know if you want help backporting these patches..
I've backported them to 3.18 with no problems, thanks.
greg k-h
prev parent reply other threads:[~2017-11-06 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 17:01 [stable] drm/msm: Fix potential buffer overflow issue Ben Hutchings
2017-11-03 22:54 ` Rob Clark
2017-11-06 7:56 ` Greg KH [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=20171106075635.GA18507@kroah.com \
--to=greg@kroah.com \
--cc=ben@decadent.org.uk \
--cc=dan.carpenter@oracle.com \
--cc=donglil@codeaurora.org \
--cc=jcrouse@codeaurora.org \
--cc=robdclark@gmail.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 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).