From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: linux-rdma@vger.kernel.org, Daniel Jurgens <danielj@mellanox.com>,
Paul Moore <paul@paul-moore.com>, Don Dutile <ddutile@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH rdma-rc 1/2] IB/core: Only enforce security for InfiniBand
Date: Wed, 22 Nov 2017 18:49:07 +0200 [thread overview]
Message-ID: <20171122164907.GD29104@mtr-leonro.local> (raw)
In-Reply-To: <20171121102618.31216-2-leon@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Tue, Nov 21, 2017 at 12:26:17PM +0200, Leon Romanovsky wrote:
> From: Daniel Jurgens <danielj@mellanox.com>
>
> For now the only LSM security enforcement mechanism available is
> specific to InfiniBand. Bypass enforcement for non-IB link types.
> This fixes a regression where modify_qp fails for iWARP because
> querying the PKEY returns -EINVAL.
>
> Cc: Paul Moore <paul@paul-moore.com>
> Cc: Don Dutile <ddutile@redhat.com>
> Cc: stable@vger.kernel.org
> Reported-by: Potnuri Bharat Teja <bharat@chelsio.com>
> Fixes: d291f1a65232("IB/core: Enforce PKey security on QPs")
> Fixes: 47a2b338fe63("IB/core: Enforce security on management datagrams")
> Signed-off-by: Daniel Jurgens <danielj@mellanox.com>
> Reviewed-by: Parav Pandit <parav@mellanox.com>
> Tested-by: Potnuri Bharat Teja <bharat@chelsio.com>
> Signed-off-by: Leon Romanovsky <leon@kernel.org>
> ---
> drivers/infiniband/core/security.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
Please drop this patch, I mistakenly cut it.
It doesn't contain the whole fix now, I'll respin.
Thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-11-22 16:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171121102618.31216-1-leon@kernel.org>
2017-11-21 10:26 ` [PATCH rdma-rc 1/2] IB/core: Only enforce security for InfiniBand Leon Romanovsky
2017-11-21 10:44 ` Mark Bloch
2017-11-21 13:22 ` Leon Romanovsky
2017-11-21 13:56 ` Mark Bloch
2017-11-21 15:14 ` Jason Gunthorpe
2017-11-21 15:33 ` Mark Bloch
2017-11-21 15:36 ` Jason Gunthorpe
2017-11-21 15:37 ` Daniel Jurgens
2017-11-21 16:04 ` Jason Gunthorpe
2017-11-21 16:34 ` Leon Romanovsky
2017-11-21 16:36 ` Jason Gunthorpe
2017-11-21 16:48 ` Leon Romanovsky
2017-11-21 17:10 ` Jason Gunthorpe
2017-11-21 18:16 ` Don Dutile
2017-11-21 18:57 ` Jason Gunthorpe
2017-11-21 20:40 ` Leon Romanovsky
2017-11-21 18:15 ` Don Dutile
2017-11-21 13:56 ` Daniel Jurgens
2017-11-22 16:49 ` Leon Romanovsky [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=20171122164907.GD29104@mtr-leonro.local \
--to=leon@kernel.org \
--cc=danielj@mellanox.com \
--cc=ddutile@redhat.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=stable@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