SELinux-Refpolicy Archive on
 help / color / Atom feed
From: Stephen Smalley <>
To: Daniel Jurgens <>,
	Paul Moore <>,
	"" <>,
	Lukas Vrabec <>,
	Chris PeBenito <>
Subject: Re: IB pkey policy problem found via the selinux-testsuite
Date: Tue, 3 Sep 2019 10:45:53 -0400
Message-ID: <> (raw)
In-Reply-To: <>

On 9/3/19 10:30 AM, Daniel Jurgens wrote:
> On 8/27/2019 12:24 PM, Paul Moore wrote:
>> On Thu, Feb 28, 2019 at 4:58 PM Paul Moore <> wrote:
>>> On Wed, Feb 13, 2019 at 4:35 PM Paul Moore <> wrote:
>>>> Hello all,
>>>> On a fully up-to-date Rawhide system you need the following line added
>>>> to the policy/test_ibpkey.te file to get a clean run of the
>>>> selinux-testsuite:
>>>>    allow test_ibpkey_access_t self:capability { ipc_lock };
>>>> The breakage doesn't appear to be due to a kernel change (previously
>>>> working kernels now fail), or a Fedora Rawhide policy change (nothing
>>>> relevant changed since the last clean run), but I did notice that my
>>>> libibverbs package was updated just prior to the breakage.  I haven't
>>>> had the time to dig into the library code, but I expect that to be the
>>>> source of the problem.
>>> Just to be clear, I don't believe this breakage is limited to the test
>>> suite, I expect any users of the SELinux IB hooks will run into this
>>> problem.  I believe we need to update the upstream and distro
>>> policies.
>> A ping to bring this issue back to the top of the mailing list.
> Hi Paul, I looked in the libraries and don't see explicit use of mlock. Maybe there was a change to use that access control for get_user_pages? That doesn't really jive with previously working kernels no longer working though.

It would be useful to see the audit messages for that ipc_lock denial, 
including the SYSCALL record.

There are a number of kernel operations that can trigger ipc_lock checks,

Several of those are infiniband-specific.

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 21:35 Paul Moore
2019-02-28 21:58 ` Paul Moore
2019-08-27 17:24   ` Paul Moore
2019-09-03 14:30     ` Daniel Jurgens
2019-09-03 14:45       ` Stephen Smalley [this message]
2019-09-04 22:32         ` Paul Moore
2019-09-05 12:07           ` Stephen Smalley

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

SELinux-Refpolicy Archive on

Archives are clonable:
	git clone --mirror selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ \
	public-inbox-index selinux-refpolicy

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox