All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH v6 2/2] selftests/bpf: Verify task_setscheduler LSM hook parameters
Date: Thu, 19 Nov 2026 04:13:55 +0000	[thread overview]
Message-ID: <sashiko-outbox-222436@kernel.org> (raw)
In-Reply-To: <20261119040705.684987-3-atomlin@atomlin.com>

> Extend the BPF LSM selftest to attach to the task_setscheduler hook and
> exercise scheduling policy updates via sched_setscheduler(), parameter
> updates via sched_setparam() and sched_setattr() with
> SCHED_FLAG_KEEP_POLICY, CPU affinity changes via sched_setaffinity(),
> and child timer slack updates via /proc/[pid]/timerslack_ns. Verify that
> the hook observes the expected sched_attr and cpumask arguments across
> each path, including the resolved scheduling policy and effective
> SCHED_FLAG_RESET_ON_FORK state for parameter-only updates as well as
> NULL pointers when an argument does not apply, and that returning -EPERM
> denies each operation.
> 
> Also add verifier test cases confirming that dereferencing the nullable
> attr or in_mask parameters without an explicit NULL check is rejected by
> the BPF verifier.
> 
> Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261119040705.684987-1-atomlin@atomlin.com?part=2


  reply	other threads:[~2026-11-19  4:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  4:07 [PATCH v6 0/2] security: Expand task_setscheduler LSM hook Aaron Tomlin
2026-11-19  4:07 ` [PATCH v6 1/2] " Aaron Tomlin
2026-11-19  4:22   ` sashiko-bot
2026-11-19  4:07 ` [PATCH v6 2/2] selftests/bpf: Verify task_setscheduler LSM hook parameters Aaron Tomlin
2026-11-19  4:13   ` sashiko-bot [this message]
2026-11-19  4:52   ` bot+bpf-ci

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-222436@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-security-module@vger.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.