stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Hansen <dave@sr71.net>
Cc: kirill.shutemov@linux.intel.com, dave.hansen@linux.intel.com,
	luto@amacapital.net, tglx@linutronix.de, x86@kernel.org,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [4.2 fix] x86, mpx: do not set ->vm_ops on mpx VMAs
Date: Fri, 31 Jul 2015 17:02:28 -0700	[thread overview]
Message-ID: <20150801000228.GA26014@kroah.com> (raw)
In-Reply-To: <20150720212958.305CC3E9@viggo.jf.intel.com>

On Mon, Jul 20, 2015 at 02:29:58PM -0700, Dave Hansen wrote:
> 
> (sorry for the spam, I screwed up the stable@ address).
> 
> BTW, thanks to Kirill for doing this patch!  He posted it to LKML
> but we need to ensure it is picked up for 4.2 and any -stable
> kernels where this commit is applied:
> 
>     	6b7339f4: mm: avoid setting up anonymous pages into file mapping
> 
> That broke MPX support because MPX sets a vma->vm_ops on an
> anonymous VMA.  We need this patch to make it work again,
> basically removing MPX's use of ->vm_ops.  Kirill made me aware
> of this long ago, but I didn't double-check that his fix got
> submitted and merged.
> 
> I (Dave) fixed up a minor merge conflict and added the
> try_unmap_single_bt() use of is_mpx_vma() (which were added
> post-4.1).
> 
> Note for -stable: The first hunk may not apply cleanly because of
> other activity in arch/x86/mm/mmap.c, but should be trivial to
> apply by hand.  Hunk #5 on mpx.c is only present on 4.2-rc kernels.

Can someone send a version that is known to apply, you don't want to
rely on me to get it right :)

thanks,

greg k-h

  reply	other threads:[~2015-08-01  0:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 21:29 [PATCH] [4.2 fix] x86, mpx: do not set ->vm_ops on mpx VMAs Dave Hansen
2015-08-01  0:02 ` Greg KH [this message]
2015-08-03 10:34   ` Kirill A. Shutemov
2015-08-03 16:19     ` Greg KH
2015-08-03 19:40       ` Kirill A. Shutemov
2015-08-03 20:36         ` Greg KH
2015-08-03 21:39           ` Kirill A. Shutemov
2015-08-06 23:35             ` Greg KH
2015-08-10  9:05             ` Luis Henriques

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=20150801000228.GA26014@kroah.com \
    --to=greg@kroah.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@sr71.net \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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).