linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Tony Luck <tony.luck@intel.com>,
	Doug Ledford <dledford@redhat.com>,
	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] IB/core: Add mitigation for Spectre V1
Date: Tue, 30 Jul 2019 21:28:01 -0700	[thread overview]
Message-ID: <20190731042801.GA2179@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <95f5cf70-1a1d-f48c-efac-f389360f585e@embeddedor.com>

On Tue, Jul 30, 2019 at 06:52:12PM -0500, Gustavo A. R. Silva wrote:
> 
> 
> On 7/30/19 3:24 PM, Tony Luck wrote:
> > Some processors may mispredict an array bounds check and
> > speculatively access memory that they should not. With
> > a user supplied array index we like to play things safe
> > by masking the value with the array size before it is
> > used as an index.
> > 
> > Signed-off-by: Tony Luck <tony.luck@intel.com>
> > ---
> > 
> > [I don't have h/w, so just compile tested]
> > 
> >  drivers/infiniband/core/user_mad.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/drivers/infiniband/core/user_mad.c b/drivers/infiniband/core/user_mad.c
> > index 9f8a48016b41..fdce254e4f65 100644
> > --- a/drivers/infiniband/core/user_mad.c
> > +++ b/drivers/infiniband/core/user_mad.c
> > @@ -49,6 +49,7 @@
> >  #include <linux/sched.h>
> >  #include <linux/semaphore.h>
> >  #include <linux/slab.h>
> > +#include <linux/nospec.h>
> >  
> >  #include <linux/uaccess.h>
> >  
> > @@ -888,6 +889,7 @@ static int ib_umad_unreg_agent(struct ib_umad_file *file, u32 __user *arg)
> >  	mutex_lock(&file->port->file_mutex);
> >  	mutex_lock(&file->mutex);
> >  
> > +	id = array_index_nospec(id, IB_UMAD_MAX_AGENTS);
> 
> This is wrong. This prevents the below condition id >= IB_UMAD_MAX_AGENTS
> from ever being true. And I don't think this is what you want.

Ah Yea...  FWIW this would probably never be hit.

Tony; split the check?

	if (id >= IB_UMAD_MAX_AGENTS) {
		ret = -EINVAL;
		goto out;
	}

	id = array_index_nospec(id, IB_UMAD_MAX_AGENTS);

	if (!__get_agent(file, id)) {
		ret = -EINVAL;
		goto out;
	}

Ira

> 
> >  	if (id >= IB_UMAD_MAX_AGENTS || !__get_agent(file, id)) {
> >  		ret = -EINVAL;
> >  		goto out;
> > 
> 
> --
> Gustavo

  reply	other threads:[~2019-07-31  4:28 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 [this message]
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

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=20190731042801.GA2179@iweiny-DESK2.sc.intel.com \
    --to=ira.weiny@intel.com \
    --cc=dledford@redhat.com \
    --cc=gustavo@embeddedor.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).