From: sashiko-bot@kernel.org
To: linux-security-module@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] selftests/bpf: Test pathname open enforcement
Date: Fri, 20 Nov 2026 09:57:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-224899@kernel.org> (raw)
In-Reply-To: <20261120094820.11929-3-tasos.papagiannnis@gmail.com>
> Verify that the hook sees the raw symlink pathname and the dirfd base.
> Check denials before creation and truncation and on O_PATH and O_TMPFILE
> opens. Check that -ECHILD makes the VFS retry the open with references.
>
> Signed-off-by: Anastasios Papagiannis <tasos.papagiannnis@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261120094820.11929-1-tasos.papagiannnis@gmail.com?part=2
prev parent reply other threads:[~2026-11-20 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 9:48 [RFC PATCH 0/2] security: Add pre-lookup pathname open check Anastasios Papagiannis
2026-11-20 9:48 ` [RFC PATCH 1/2] security: Add hook for unresolved pathname opens Anastasios Papagiannis
2026-11-20 10:00 ` sashiko-bot
2026-11-20 9:48 ` [RFC PATCH 2/2] selftests/bpf: Test pathname open enforcement Anastasios Papagiannis
2026-11-20 9:57 ` 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-224899@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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