From: sashiko-bot@kernel.org
To: selinux@vger.kernel.org
Subject: Re: [RFC PATCH v2] projects/selinux: enroll the SELinux userspace project
Date: Fri, 13 Nov 2026 14:08:58 +0000 [thread overview]
Message-ID: <sashiko-outbox-212961@kernel.org> (raw)
In-Reply-To: <20261113140145.91850-2-stephen.smalley.work@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Medium] projects/selinux: Dockerfile omits newrole build dependencies
and flags
- [Low] projects/selinux: patch_guidelines.md retains template
boilerplate and typo
--
commit e4b3796eb9b6ee214884a7fed6793943a0dfc672
Author: Stephen Smalley <stephen.smalley.work@gmail.com>
projects/selinux: enroll the SELinux userspace project
This commit enrolls the SELinux userspace project in oss-scanner by adding
its project configuration, build Dockerfile, threat model, and patch and
report guidelines.
> diff --git a/projects/selinux/Dockerfile b/projects/selinux/Dockerfile
> new file mode 100644
> index 0000000000000..ce909fdf5c285
> --- /dev/null
> +++ b/projects/selinux/Dockerfile
> @@ -0,0 +1,35 @@
> +FROM ubuntu:latest
> +ENV DEBIAN_FRONTEND=noninteractive
> +RUN apt-get update && apt-get install -y --no-install-recommends \
> + ca-certificates build-essential pkg-config git python3 \
> + bison \
> + flex \
> + gawk \
> + gcc \
> + gettext \
> + libaudit-dev \
> + libbz2-dev \
> + libcap-dev \
> + libcap-ng-dev \
> + libcunit1-dev \
> + libdbus-glib-1-dev \
> + libpcre2-dev \
> + ruby-dev \
> + swig \
> + xmlto \
> + python3-build \
> + python3-dev \
> + python3-pip \
> + python3-setuptools \
> + python3-wheel \
> + swig \
> + && rm -rf /var/lib/apt/lists/*
> +
> +# scanner contract: the checkout lives inside the image, at /src
> +COPY . /src
> +WORKDIR /src
> +
> +RUN make -k DEBUG=1 DESTDIR=/src/build install install-pywrap
[Severity: Medium]
Should this Dockerfile install libpam0g-dev and pass AUDIT_LOG_PRIV=y,
NAMESPACE_PRIV=y, and LSPP_PRIV=y to make?
projects/selinux/threat_model.md prioritizes policycoreutils/newrole first
and notes that its privileged behavior depends on those build flags.
However, policycoreutils/Makefile skips building newrole unless PAM headers
(/usr/include/security/pam_appl.h from libpam0g-dev) are present, and
policycoreutils/newrole/Makefile only compiles the privileged audit,
namespace, and LSPP code paths when those flags are enabled, leaving
newrole unbuilt in /src/build.
Also, swig is listed twice in the apt-get install package list.
> diff --git a/projects/selinux/patch_guidelines.md b/projects/selinux/patch_guidelines.md
> new file mode 100644
> index 0000000000000..7688835f95eff
> --- /dev/null
> +++ b/projects/selinux/patch_guidelines.md
> @@ -0,0 +1,13 @@
> +# How we would like patches made
> +
> +## Size and scope of a fix
> +as narrow as possible: change only the faulty function, no refactoring
> +
> +## Code style
> +format with the .clang-format at the root
> +
> +## Tests
> +add a regression test in a new file under the per-component tests/
> +
> +## Branch and commit message
> +against the main branch; subject line in the form 'component: what changed'"
[Severity: Low]
Does patch_guidelines.md retain placeholder text from the oss-scanner
example template? The selinuxproject/selinux repository has no
.clang-format at the root or uniform per-component tests/ directories, and
the last line has a stray trailing double quote while omitting the
project's Signed-off-by requirement.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113140145.91850-2-stephen.smalley.work@gmail.com?part=1
prev parent reply other threads:[~2026-11-13 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 14:01 [RFC PATCH v2] projects/selinux: enroll the SELinux userspace project Stephen Smalley
2026-11-13 14:08 ` sashiko-bot [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=sashiko-outbox-212961@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=selinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.