linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Vinit Agnihotri <vinita@ryussi.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [question] ibv_reg_mr() returning EACCESS
Date: Fri, 15 Nov 2019 10:12:10 -0400	[thread overview]
Message-ID: <20191115141210.GC4055@ziepe.ca> (raw)
In-Reply-To: <141f4c07-b7f1-1355-7ff7-d62605ee63b5@ryussi.com>

On Fri, Nov 15, 2019 at 09:27:40AM +0530, Vinit Agnihotri wrote:
> Hi,
> 
> I am trying to use setfsgid()/setfssid() calls to ensure proper access check
> for linux users.
> 
> However if user is non-root then ibv_reg_mr() returns EACCESS. While I am
> sure I am calling ibv_reg_mr()
> 
> as root user, not sure why it still returns EACCESS.
> 
> While going through libibverbs sources I realize EACCESS might be returned
> by this call:
> 
> if (write(pd->context->cmd_fd, cmd, cmd_size) != cmd_size)
>         return errno;
> 
> Can anyone provide any insight into this behavior? Does calling these
> systems calls in threads can affect
> 
> entire process? I checked /dev/infiniband/* has appropriate privileges.

This is a security limitation, if you want do this flow you need a new
enough kernel and rdma-core to support the ioctl() scheme for calling
verbs

Jason

  reply	other threads:[~2019-11-15 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  3:57 [question] ibv_reg_mr() returning EACCESS Vinit Agnihotri
2019-11-15 14:12 ` Jason Gunthorpe [this message]
2019-11-18  4:59   ` Vinit Agnihotri
2019-11-19 23:34     ` Jason Gunthorpe
2019-11-20  4:05       ` Vinit Agnihotri

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=20191115141210.GC4055@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=vinita@ryussi.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).