From: Doug Ledford <dledford@redhat.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Luck, Tony" <tony.luck@intel.com>,
Ira Weiny <ira.weiny@intel.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Parav Pandit <parav@mellanox.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] IB/core: Add mitigation for Spectre V1
Date: Wed, 31 Jul 2019 15:22:19 -0400 [thread overview]
Message-ID: <96896eaeaac7cefed65098da268f92e96db69591.camel@redhat.com> (raw)
In-Reply-To: <c48b7b8db29126fe8991a4b65ed0b793f10501fa.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Wed, 2019-07-31 at 14:52 -0400, Doug Ledford wrote:
> On Wed, 2019-07-31 at 12:52 -0500, Gustavo A. R. Silva wrote:
> > This is insufficient. The speculation windows are large:
> >
> > "Speculative execution on modern CPUs can run several
> > hundred instructions ahead." [1]
> >
> > [1] https://spectreattack.com/spectre.pdf
>
> Thanks, I'll take a look at that. That issue aside, returning without
> wasting time on two mutexes is still better IMO, so I like my patch
> more
> than the proposed one. Tony, would you like to resubmit?
>
Never mind, I took your V2 and fixed it up like I wanted. Patch
applied, thanks.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-07-31 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 20:24 [PATCH] IB/core: Add mitigation for Spectre V1 Tony Luck
2019-07-30 23:34 ` Ira Weiny
2019-07-30 23:52 ` Gustavo A. R. Silva
2019-07-31 4:28 ` Ira Weiny
2019-07-31 4:39 ` [PATCH V2] " Luck, Tony
2019-07-31 14:52 ` Doug Ledford
2019-07-31 17:52 ` Gustavo A. R. Silva
2019-07-31 18:52 ` Doug Ledford
2019-07-31 19:22 ` Doug Ledford [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=96896eaeaac7cefed65098da268f92e96db69591.camel@redhat.com \
--to=dledford@redhat.com \
--cc=gustavo@embeddedor.com \
--cc=ira.weiny@intel.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).