All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, bp@suse.de, dsafonov@virtuozzo.com,
	kirill.shutemov@linux.intel.com, luto@amacapital.net,
	tglx@linutronix.de, torvalds@linux-foundation.org,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "x86/elf: Remove the unnecessary ADDR_NO_RANDOMIZE checks" has been added to the 4.12-stable tree
Date: Wed, 23 Aug 2017 16:08:10 +0200	[thread overview]
Message-ID: <20170823140809.GA9209@redhat.com> (raw)
In-Reply-To: <20170822201544.GA19520@kroah.com>

On 08/22, Greg KH wrote:
>
> On Mon, Aug 21, 2017 at 04:21:34PM +0200, Oleg Nesterov wrote:
> > On 08/20, gregkh@linuxfoundation.org wrote:
> > >
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> >
> > Yes, I think this is not -stable material, this is really minor cleanup.
>
> But I'm pretty sure it is needed for the patch after this one in the
> series, right?

Confused... it was 2/2, afaics nothing depends on this change. In particular, 1/2
47ac5484fd961420e5ec0bb5b972fde381f57365 ("x86: Fix norandmaps/ADDR_NO_RANDOMIZE")
doesn't depend.

Nevermind, if you have already applied this cleanup it should not hurt, it is
very simple and hopefully "obviously correct".

Oleg.

      reply	other threads:[~2017-08-23 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20 19:01 Patch "x86/elf: Remove the unnecessary ADDR_NO_RANDOMIZE checks" has been added to the 4.12-stable tree gregkh
2017-08-21 14:21 ` Oleg Nesterov
2017-08-22 20:15   ` Greg KH
2017-08-23 14:08     ` Oleg Nesterov [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=20170823140809.GA9209@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=dsafonov@virtuozzo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=luto@amacapital.net \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.