public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miles Chen <miles.chen@mediatek.com>
Cc: stable@vger.kernel.org
Subject: Re: backport a patch for Linux 3.18
Date: Thu, 31 Aug 2017 07:58:18 +0200	[thread overview]
Message-ID: <20170831055818.GA23168@kroah.com> (raw)
In-Reply-To: <1504064056.30912.21.camel@mtkswgap22>

On Wed, Aug 30, 2017 at 11:34:16AM +0800, Miles Chen wrote:
> Hi reviewers,
> 
> I suggest to backport a commit to Linux 3.18 stable tree.
> Reason: KASAN reports a out-of-bound write issue when a large size
> allocation is made from drivers through user-space.
> 
> 
> commit: 67a2e213e7e937c41c52ab5bc46bf3f4de469f6e
> subject: mm: cma: fix incorrect type conversion for size during dma
> allocation
> kernel version to apply to: Linux 3.18

Now applied, along with a number of other cma fixes that 3.18 really
should have as well (that were dependancies of this patch in order to
apply "cleanly".)

thanks,

greg k-h

      reply	other threads:[~2017-08-31  5:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  3:34 backport a patch for Linux 3.18 Miles Chen
2017-08-31  5:58 ` 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=20170831055818.GA23168@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=miles.chen@mediatek.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