Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BD55DC43381 for ; Wed, 13 Feb 2019 21:35:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8073720842 for ; Wed, 13 Feb 2019 21:35:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=paul-moore-com.20150623.gappssmtp.com header.i=@paul-moore-com.20150623.gappssmtp.com header.b="kBU+Jd0Y" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389554AbfBMVfZ (ORCPT ); Wed, 13 Feb 2019 16:35:25 -0500 Received: from mail-lf1-f66.google.com ([209.85.167.66]:38878 "EHLO mail-lf1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729545AbfBMVfZ (ORCPT ); Wed, 13 Feb 2019 16:35:25 -0500 Received: by mail-lf1-f66.google.com with SMTP id n15so2948616lfe.5 for ; Wed, 13 Feb 2019 13:35:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paul-moore-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=2+7cAkZjb0EpLI0oNagTM30oUolGQDJ6mTqrPIDH5AA=; b=kBU+Jd0Y4H3rTfxmYQ6KNEEfSckWdvcajkmWU+GQGPe/70f9p0V2Ph612CupKwtCkW fwFn4c/z1ZLhQyiuahgdeD1XcwVlP8dsWDnGCVv/vfyJrja8yujsemivgc+XtU3AVgZM fyMWwC8t4Ci2F0pUze9Rrv9h6HZK+ASmaPUhSfbrHpAzLUym9IcJGKgHoLQnENyNDu2Z ACE1iulLuQ8r/bB5kKis7SHZI4I6qG2rXWOTM8+xeT4f85BDAfNo0I2a9WuqJ4Yt6+WX TcVoYiZLkVRuzunMBip1c2R6LukrMObFt3UqmWZjFR5CW5+KKCtzdeZNEL5HeRZ6Udjs ML0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=2+7cAkZjb0EpLI0oNagTM30oUolGQDJ6mTqrPIDH5AA=; b=XJQFB2gdGhnhJJ25JYDy6YV3gcLZYvWJux4XGKmsu+wYbCyDSwUYMFevuHsjCDk3vH bOuL6c/siB7xOTP5ihi/6uqt+mxBLMBl4wLyvHF+fmIixd5jmEssoGfjZPlcB9lYxv2D xUb7oX3SAQbwRwCgwSBoi5TUPgBJvjGtHYLkqnZ8+sgVGMAPedEb8d+tsGLDRrGyMjFF OdKhSXzvW8imsR8EtulvbQ+cKaNe/vaWxRlhHLoZXpR91+UJoKcvtP+yl+u90jIFPm/O Kt7G7CkoshfmK3ancspBf+Bb83s5//62MbPKaGKwANHoc8gSkzSQUDK+TmCxEQHzBrne b1yQ== X-Gm-Message-State: AHQUAuawZ+sNtkxZgS5H8XHK1R5LqTuAV0KRr8AHPg6kTKqvx1+lxF5N VLnvcNWa4Kdts3VAPatUpdtFnz6CGnvMgZ8WkX1p X-Google-Smtp-Source: AHgI3IYkF83kGyoCoAqt+UOg5hHJAmPvLx0AJ1FeNoTimmvIwIR2zFOCO+1g2VeLTMydy8mYTMwCpApDpB8+e6z1J6Q= X-Received: by 2002:a19:384c:: with SMTP id d12mr130348lfj.105.1550093722741; Wed, 13 Feb 2019 13:35:22 -0800 (PST) MIME-Version: 1.0 From: Paul Moore Date: Wed, 13 Feb 2019 16:35:11 -0500 Message-ID: Subject: IB pkey policy problem found via the selinux-testsuite To: selinux@vger.kernel.org, selinux-refpolicy@vger.kernel.org Cc: Lukas Vrabec , danielj@mellanox.com Content-Type: text/plain; charset="UTF-8" Sender: selinux-refpolicy-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: selinux-refpolicy@vger.kernel.org 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. -- paul moore www.paul-moore.com