All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: stable <stable@vger.kernel.org>
Subject: Re: [stable] DMA-on-stack fixes
Date: Wed, 19 Apr 2017 16:42:06 +0200	[thread overview]
Message-ID: <20170419144206.GA2793@kroah.com> (raw)
In-Reply-To: <1492611302.31767.1.camel@decadent.org.uk>

On Wed, Apr 19, 2017 at 03:15:02PM +0100, Ben Hutchings wrote:
> On Wed, 2017-04-19 at 14:16 +0200, Greg Kroah-Hartman wrote:
> > On Tue, Apr 18, 2017 at 01:49:41AM +0100, Ben Hutchings wrote:
> > > Brad Spengler pointed out these fixes elsewhere:
> > > 
> > > 43fab9793c1f [media] dvb-usb: don't use stack for firmware load
> > > 67b0503db9c2 [media] dvb-usb-firmware: don't do DMA on stack
> > > 3f190e3aec21 [media] cxusb: Use a dma capable buffer also for reading
> > > c4baad50297d virtio-console: avoid DMA from stack
> > > 
> > > For 4.9, the first one needs some adjustment - use the attached patch.
> > > The rest apply cleanly.
> > > 
> > > For 4.10, you can skip the first two as they've already been applied.
> > 
> > Thanks for this shorter list.��I'll go through the rest of the list of
> > patches that Brad pointed out on oss-security.
> > 
> > Oh, and you did notice he said that
> > a4866aa81251 ("mm: Tighten x86 /dev/mem with zeroing reads")
> > should be applied to stable kernels, right?��I've queued it up for the
> > ones I manage.
> 
> Yes, though it's not a meaningful security fix by itself.

What do you mean "by itself"?  Is there something else that needs to be
added here, or just that the patch doesn't really change all that much?

thanks,

greg k-h

  reply	other threads:[~2017-04-19 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  0:49 [stable] DMA-on-stack fixes Ben Hutchings
2017-04-19 12:16 ` Greg Kroah-Hartman
2017-04-19 14:15   ` Ben Hutchings
2017-04-19 14:42     ` Greg Kroah-Hartman [this message]
2017-04-19 15:57       ` Ben Hutchings

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=20170419144206.GA2793@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ben@decadent.org.uk \
    --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.