From: Wei Gao via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v11 0/2] open16: allow restricted O_CREAT of FIFOs and regular files
Date: Tue, 21 Jul 2026 07:41:27 +0000 [thread overview]
Message-ID: <20260721074146.2779-1-wegao@suse.com> (raw)
In-Reply-To: <20260707054804.24232-2-wegao@suse.com>
v10->v11:
* tst_uid.h: Moved kernel-doc comments above the macros to fix parser warnings.
* tst_uid.c: Removed TERRNO from tst_get_free_gid_ success path to avoid misleading output.
* open16: Added group-writable sticky directories to the commit message to match the test.
Wei Gao (2):
lib: New library function tst_get_free_uid
open16: allow restricted O_CREAT of FIFOs and regular files
include/tst_uid.h | 29 ++++-
lib/tst_uid.c | 30 ++++-
runtest/syscalls | 1 +
testcases/kernel/syscalls/open/.gitignore | 1 +
testcases/kernel/syscalls/open/open16.c | 135 ++++++++++++++++++++++
5 files changed, 191 insertions(+), 5 deletions(-)
create mode 100644 testcases/kernel/syscalls/open/open16.c
--
2.54.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-07-21 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://patchwork.ozlabs.org/project/ltp/patch/20260707022959.24088-2-wegao@suse.com/>
2026-07-07 5:47 ` [LTP] [PATCH v10 0/2] open16: allow restricted O_CREAT of FIFOs and regular files Wei Gao via ltp
2026-07-07 5:47 ` [LTP] [PATCH v10 1/2] lib: New library function tst_get_free_uid Wei Gao via ltp
2026-07-07 7:48 ` [LTP] " linuxtestproject.agent
2026-07-21 7:41 ` Wei Gao via ltp [this message]
2026-07-21 7:41 ` [LTP] [PATCH v11 1/2] " Wei Gao via ltp
2026-07-21 8:38 ` [LTP] " linuxtestproject.agent
2026-07-21 7:41 ` [LTP] [PATCH v11 2/2] open16: allow restricted O_CREAT of FIFOs and regular files Wei Gao via ltp
2026-07-21 8:22 ` [LTP] [PATCH v11 0/2] " Andrea Cervesato via ltp
2026-07-21 8:55 ` Wei Gao via ltp
2026-07-07 5:47 ` [LTP] [PATCH v10 2/2] " Wei Gao via ltp
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=20260721074146.2779-1-wegao@suse.com \
--to=ltp@lists.linux.it \
--cc=wegao@suse.com \
/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.