From: Willy Tarreau <w@1wt.eu>
To: mancha security <mancha1@zoho.com>
Cc: stable@vger.kernel.org, jslaby@suse.cz, edumazet@google.com
Subject: Re: [PATCH 3.10.x/3.12.x] net: challenge ACK side-channel attack mitigation (CVE-2016-5696)
Date: Fri, 19 Aug 2016 07:50:23 +0200 [thread overview]
Message-ID: <20160819055023.GI17944@1wt.eu> (raw)
In-Reply-To: <20160819054825.GB7317@zoho.com>
On Fri, Aug 19, 2016 at 05:48:25AM +0000, mancha security wrote:
> On Fri, Aug 19, 2016 at 07:19:22AM +0200, Willy Tarreau wrote:
> >
> > That's very kind of you, but Chas Williams already provided us with this
> > backport. I hope to be able to work on 3.10.103 this week-end.
> >
> > Thanks!
> > Willy
>
> Ah, thanks for the update.
>
> Cheers!
>
> --mancha
>
> PS My patch is probably better :)
They're the same except that you added a macro to define the random
function while Chas used the already provided reciprocal_divide().
Willy
prev parent reply other threads:[~2016-08-19 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 22:33 [PATCH 3.10.x/3.12.x] net: challenge ACK side-channel attack mitigation (CVE-2016-5696) mancha security
2016-08-19 5:19 ` Willy Tarreau
2016-08-19 5:48 ` mancha security
2016-08-19 5:50 ` Willy Tarreau [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=20160819055023.GI17944@1wt.eu \
--to=w@1wt.eu \
--cc=edumazet@google.com \
--cc=jslaby@suse.cz \
--cc=mancha1@zoho.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox