All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Mike Galbraith <efault@gmx.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT PULL] x86-refcount fix for v4.14-rc3
Date: Wed, 27 Sep 2017 14:02:39 +0200	[thread overview]
Message-ID: <20170927120239.7rac2d77bykitfjy@gmail.com> (raw)
In-Reply-To: <CAGXu5jKshVvuTyVycAbAYSVx5KU9nSBHUw+vmSc8p-2JdBhftw@mail.gmail.com>


* Kees Cook <keescook@chromium.org> wrote:

> On Wed, Sep 27, 2017 at 12:57 PM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * Kees Cook <keescook@chromium.org> wrote:
> >
> >> Hi,
> >>
> >> Please pull this x86-refcount fix for v4.14-rc3. This restores the x86
> >> fast-refcount protection after fixing a corner case that was found late
> >> before the merge window opened. This was the only problem seen during
> >> the protection's life in linux-next, so getting this into v4.14 is
> >> highly desired.
> >
> > No, this is clearly v4.15 material.
> 
> Given the long bake time in linux-next (with only the one bug), and
> that the fix was done weeks ago, why the delay?

Because it's essentially enabling a new feature and the merge window is over.
I'll apply them in 1-2 days.

Thanks,

	Ingo

      reply	other threads:[~2017-09-27 12:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 10:29 [GIT PULL] x86-refcount fix for v4.14-rc3 Kees Cook
2017-09-27 10:57 ` Ingo Molnar
2017-09-27 11:47   ` Kees Cook
2017-09-27 12:02     ` Ingo Molnar [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=20170927120239.7rac2d77bykitfjy@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=efault@gmx.de \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.