From: Potnuri Bharat Teja <bharat-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
To: Daniel Jurgens <danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"leon-XVmvHMARGATQT0dZR+AlfA@public.gmane.org"
<leon-XVmvHMARGATQT0dZR+AlfA@public.gmane.org>,
SWise OGC
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
Raju Rangoju <rajur-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: Re: kernel space iWARP broken with CONFIG_SECURITY_INFINIBAND enabled
Date: Thu, 16 Nov 2017 13:10:54 +0530 [thread overview]
Message-ID: <20171116074049.GB9284@chelsio.com> (raw)
In-Reply-To: <8ac43c6a-e2d9-572e-b4bf-03cdf3be57a8-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Wednesday, November 11/15/17, 2017 at 23:51:08 +0530, Daniel Jurgens wrote:
> On 11/15/2017 7:15 AM, Potnuri Bharat Teja wrote:
> > Hi all,
> > With CONFIG_SECURITY_INFINIBAND kernel config option enabled iWARP kernel
> > space applications are failing at rdma_create_qp(). Apparantly SELinux
> > support for Infiniband RDMA caused this regression.
> >
> > Here is the failure with NVMEof discovery:
> > [ 129.294943] nvme nvme0: rdma_resolve_addr wait failed (-22).
> >
> > Failure is at ib_get_cached_pkey(), for invalid pkey_index, called by the
> > following call chain:
> > rdma_create_qp()-> cma_init_conn_qp()-> ib_modify_qp()->
> > ib_security_modify_qp()-> check_qp_port_pkey_settings()->
> > get_pkey_and_subnet_prefix()
> >
> > SELinux support for Infiniband RDMA:
> > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.spinics.net%2Flists%2Flinux-rdma%2Fmsg38705.html&data=02%7C01%7Cdanielj%40mellanox.com%7C562dfe4029994b668c8808d52c2af77a%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636463485413049982&sdata=zjyS9aC9I2vRRxPyrIeLmCAl0Cg3cNJS7Tfz96Fzl%2F4%3D&reserved=0
> >
> > I am trying to understand how IB security enforcing works with iWARP.
> > From the commit messages these appears to be an IB specific changes.
> > If true, how is iw_cm supposed to handle it?
> > iWARP doesn't use or have partition keys (pkey), How is this handled by the
> > IB security enforcing changes?
> >
> > Thanks,
> > Bharat.
> >
>
> Thanks Bharat, would you mind testing a patch for me? I don't have any iWARP hardware. I'll send to you it by EOB today.
Thanks for the quick patch Daniel.
Tested the patch for iwarp and it fixes the regression.
I think this should be marked for stable as well.
Thanks,
Bharat.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-16 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 13:15 kernel space iWARP broken with CONFIG_SECURITY_INFINIBAND enabled Potnuri Bharat Teja
[not found] ` <20171115131525.GB25574-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2017-11-15 18:21 ` Daniel Jurgens
[not found] ` <8ac43c6a-e2d9-572e-b4bf-03cdf3be57a8-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-16 7:40 ` Potnuri Bharat Teja [this message]
[not found] ` <20171116074049.GB9284-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2017-11-16 14:13 ` Daniel Jurgens
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=20171116074049.GB9284@chelsio.com \
--to=bharat-ut6up61k2wzbdgjk7y7tuq@public.gmane.org \
--cc=danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=leon-XVmvHMARGATQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rajur-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.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