From: Willy Tarreau <w@1wt.eu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Kevin Christopher <kevinc@vmware.com>,
stable@vger.kernel.org, Imre Palik <imrep@amazon.de>
Subject: Re: Request security fix in -stable (upstream 2c33645d366d)
Date: Thu, 7 Jul 2016 10:28:09 +0200 [thread overview]
Message-ID: <20160707082809.GA29365@1wt.eu> (raw)
In-Reply-To: <20160707072141.GQ30921@twins.programming.kicks-ass.net>
On Thu, Jul 07, 2016 at 09:21:41AM +0200, Peter Zijlstra wrote:
> On Thu, Jul 07, 2016 at 06:40:59AM +0200, Willy Tarreau wrote:
> > > Upstream commit:
> > > (commit) 2c33645d366d13b969d936b68b9f4875b1fdddea
> > > (subject) perf/x86: Honor the architectural performance monitoring version
> > >
> > > A second commit fixes a trivial build issue introduced by the above commit:
> > > (commit) 6d6f2833bfbf296101f9f085e10488aef2601ba5
> > > (subject) perf/x86: Fix undefined shift on 32-bit kernels
>
> > Usually it is recommended to CC the patch's author and maintainers of
> > the code in question because they help with backports of fixes, and they
> > are the ones who know best if there's a risk of regression or if a fix
> > is incomplete for certain versions, so they definitely have their word
> > to say. I'm CCing Imre and Peter who were involved in this fix.
> >
> > Also we're usually careful about not backporting to older kernels
> > something which is not yet in more recent ones. Greg is traveling with
> > limited connectivity this week, so we may have to wait for him to come
> > back. The bug is not urgent anyway since it was fixed one year ago :-)
>
> No objections from my pov. they're fairly simple patches, therefore I
> would not suspect any trouble backporting this, but if there is, do
> holler.
OK, thank you Peter!
Willy
next prev parent reply other threads:[~2016-07-07 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 22:13 Request security fix in -stable (upstream 2c33645d366d) Kevin Christopher
2016-07-07 4:40 ` Willy Tarreau
2016-07-07 7:21 ` Peter Zijlstra
2016-07-07 8:28 ` Willy Tarreau [this message]
2017-10-08 21:09 ` 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=20160707082809.GA29365@1wt.eu \
--to=w@1wt.eu \
--cc=imrep@amazon.de \
--cc=kevinc@vmware.com \
--cc=peterz@infradead.org \
--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.