From: Leon Romanovsky <leonro@mellanox.com>
To: Dan Jurgens <danielj@mellanox.com>
Cc: chrisw@sous-sol.org, paul@paul-moore.com, sds@tycho.nsa.gov,
eparis@parisplace.org, dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org,
linux-rdma@vger.kernel.org, yevgenyp@mellanox.com,
liranl@mellanox.com
Subject: Re: [PATCH v4 9/9] selinux: Add a cache for quicker retreival of PKey SIDs
Date: Wed, 9 Nov 2016 09:04:55 +0200 [thread overview]
Message-ID: <20161109070455.GF27883@leon.nu> (raw)
In-Reply-To: <1478639185-47521-10-git-send-email-danielj@mellanox.com>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Tue, Nov 08, 2016 at 11:06:25PM +0200, Dan Jurgens wrote:
> From: Daniel Jurgens <danielj@mellanox.com>
>
> It is likely that the SID for the same PKey will be requested many
> times. To reduce the time to modify QPs and process MADs use a cache to
> store PKey SIDs.
>
> This code is heavily based on the "netif" and "netport" concept
> originally developed by James Morris <jmorris@redhat.com> and Paul Moore
> <paul@paul-moore.com> (see security/selinux/netif.c and
> security/selinux/netport.c for more information)
>
> issue: 736423
> Change-Id: I176c3079d5d84d06839b4f750100ac47a6081e94
It doesn't belong to commit message.
> Signed-off-by: Daniel Jurgens <danielj@mellanox.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-11-09 7:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 21:06 [PATCH v4 0/9] SELinux support for Infiniband RDMA Dan Jurgens
2016-11-08 21:06 ` [PATCH v4 1/9] IB/core: IB cache enhancements to support Infiniband security Dan Jurgens
2016-11-08 21:06 ` [PATCH v4 2/9] IB/core: Enforce PKey security on QPs Dan Jurgens
[not found] ` <1478639185-47521-1-git-send-email-danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-11-08 21:06 ` [PATCH v4 3/9] selinux lsm IB/core: Implement LSM notification system Dan Jurgens
2016-11-08 22:35 ` kbuild test robot
2016-11-08 23:41 ` Daniel Jurgens
2016-11-08 21:06 ` [PATCH v4 4/9] IB/core: Enforce security on management datagrams Dan Jurgens
2016-11-08 21:06 ` [PATCH v4 7/9] selinux: Implement Infiniband PKey "Access" access vector Dan Jurgens
2016-11-08 21:06 ` [PATCH v4 8/9] selinux: Add IB Port SMP " Dan Jurgens
2016-11-08 21:06 ` [PATCH v4 9/9] selinux: Add a cache for quicker retreival of PKey SIDs Dan Jurgens
[not found] ` <1478639185-47521-10-git-send-email-danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-11-09 5:09 ` kbuild test robot
2016-11-09 7:04 ` Leon Romanovsky [this message]
2016-11-09 14:03 ` Daniel Jurgens
2016-11-08 21:06 ` [PATCH v4 5/9] selinux: Create policydb version for Infiniband support Dan Jurgens
2016-11-08 21:06 ` [PATCH v4 6/9] selinux: Allocate and free infiniband security hooks Dan 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=20161109070455.GF27883@leon.nu \
--to=leonro@mellanox.com \
--cc=chrisw@sous-sol.org \
--cc=danielj@mellanox.com \
--cc=dledford@redhat.com \
--cc=eparis@parisplace.org \
--cc=hal.rosenstock@gmail.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=liranl@mellanox.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=sean.hefty@intel.com \
--cc=selinux@tycho.nsa.gov \
--cc=yevgenyp@mellanox.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