From: Vinit Agnihotri <vinita@ryussi.com>
To: linux-rdma@vger.kernel.org
Subject: [question] ibv_reg_mr() returning EACCESS
Date: Fri, 15 Nov 2019 09:27:40 +0530 [thread overview]
Message-ID: <141f4c07-b7f1-1355-7ff7-d62605ee63b5@ryussi.com> (raw)
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.
Thanks & Regards,
Vinit.
next reply other threads:[~2019-11-15 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 3:57 Vinit Agnihotri [this message]
2019-11-15 14:12 ` [question] ibv_reg_mr() returning EACCESS Jason Gunthorpe
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=141f4c07-b7f1-1355-7ff7-d62605ee63b5@ryussi.com \
--to=vinita@ryussi.com \
--cc=linux-rdma@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