From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752870AbdI0MCp (ORCPT <rfc822;w@1wt.eu>);
        Wed, 27 Sep 2017 08:02:45 -0400
Received: from mail-wr0-f196.google.com ([209.85.128.196]:38477 "EHLO
        mail-wr0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751287AbdI0MCn (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 27 Sep 2017 08:02:43 -0400
X-Google-Smtp-Source: AOwi7QAvGslzN3zsIdDRtWMAtTzxcIHiaK97L/GecmJjSTb+PA2WOi0pmFhyxxb3iIcziBTUTU7CXw==
Date: Wed, 27 Sep 2017 14:02:39 +0200
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
Message-ID: <20170927120239.7rac2d77bykitfjy@gmail.com>
References: <20170927102946.GA54244@beast>
 <20170927105757.4ruxlr4by6cz7lxj@gmail.com>
 <CAGXu5jKshVvuTyVycAbAYSVx5KU9nSBHUw+vmSc8p-2JdBhftw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGXu5jKshVvuTyVycAbAYSVx5KU9nSBHUw+vmSc8p-2JdBhftw@mail.gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* 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