From: jeffxu@chromium.org
To: mic@digikod.net
Cc: jorgelo@chromium.org, keescook@chromium.org,
linux-security-module@vger.kernel.org, groeck@chromium.org,
gnoack@google.com, Jeff Xu <jeffxu@google.com>
Subject: [PATCH v4 0/1] selftests/landlock: Fix selftest ptrace_test
Date: Tue, 3 Jan 2023 19:03:13 +0000 [thread overview]
Message-ID: <20230103190314.3882177-1-jeffxu@google.com> (raw)
From: Jeff Xu <jeffxu@google.com>
Landlock ptrace failed because YAMA is enabled.
This patch check YAMA value and skip related tests.
V4:
- apply can_trace_parent and can_trace_child to smaller scope.
V3:
https://lore.kernel.org/all/20221227140244.1041292-1-jeffxu@google.com
- add can_trace_parent and can_trace_child to handle yama value.
V2:
https://lore.kernel.org/all/20221213185816.3942853-1-jeffxu@chromium.org
- update from code review comments.
V1:
https://lore.kernel.org/all/20221213185816.3942853-1-jeffxu@chromium.org
- skip specific testcase according to YAMA value
V0:
https://lore.kernel.org/r/20220628222941.2642917-1-jeffxu@google.com
- skip entire ptrace when YAMA is not 0.
Jeff Xu (1):
selftests/landlock: skip ptrace_test according to YAMA
.../testing/selftests/landlock/ptrace_test.c | 48 ++++++++++++++++---
1 file changed, 42 insertions(+), 6 deletions(-)
base-commit: 963a70bee5880640d0fd83ed29dc1e7ec0d2bd4a
--
2.39.0.314.g84b9a713c41-goog
next reply other threads:[~2023-01-03 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 19:03 jeffxu [this message]
2023-01-03 19:03 ` [PATCH v4 1/1] selftests/landlock: skip ptrace_test according to YAMA jeffxu
2023-01-03 20:12 ` Guenter Roeck
2023-01-03 23:49 ` Jeff Xu
2023-01-04 3:40 ` Guenter Roeck
2023-01-09 15:29 ` Mickaël Salaün
2023-01-09 22:50 ` Jeff Xu
2023-01-10 19:04 ` Mickaël Salaün
2023-01-10 20:41 ` Jeff Xu
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=20230103190314.3882177-1-jeffxu@google.com \
--to=jeffxu@chromium.org \
--cc=gnoack@google.com \
--cc=groeck@chromium.org \
--cc=jeffxu@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
/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;
as well as URLs for NNTP newsgroup(s).