From: "Günther Noack" <gnoack3000@gmail.com>
To: linux-security-module@vger.kernel.org
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack3000@gmail.com>
Subject: [PATCH 2/2] landlock: Selftests for truncate(2) support.
Date: Thu, 7 Jul 2022 22:06:13 +0200 [thread overview]
Message-ID: <20220707200612.132705-3-gnoack3000@gmail.com> (raw)
In-Reply-To: <20220707200612.132705-1-gnoack3000@gmail.com>
These tests exercise the following scenarios:
* File with Read, Write, Truncate rights.
* File with Read, Write rights.
* File with Truncate rights.
* File with no rights.
* Directory with Truncate rights.
For each of the scenarios, both truncate() and the open() +
ftruncate() syscalls get exercised and their results checked.
In particular, the test demonstrates that opening a file for writing
is not enough to call truncate().
Signed-off-by: Günther Noack <gnoack3000@gmail.com>
---
tools/testing/selftests/landlock/fs_test.c | 80 ++++++++++++++++++++++
1 file changed, 80 insertions(+)
diff --git a/tools/testing/selftests/landlock/fs_test.c b/tools/testing/selftests/landlock/fs_test.c
index cb77eaa01c91..c3e48fd12b2b 100644
--- a/tools/testing/selftests/landlock/fs_test.c
+++ b/tools/testing/selftests/landlock/fs_test.c
@@ -2237,6 +2237,86 @@ TEST_F_FORK(layout1, reparent_rename)
ASSERT_EQ(EXDEV, errno);
}
+TEST_F_FORK(layout1, truncate)
+{
+ const struct rule rules[] = {
+ {
+ .path = file1_s1d1,
+ .access = LANDLOCK_ACCESS_FS_READ_FILE |
+ LANDLOCK_ACCESS_FS_WRITE_FILE |
+ LANDLOCK_ACCESS_FS_TRUNCATE,
+ },
+ {
+ .path = file2_s1d2,
+ .access = LANDLOCK_ACCESS_FS_READ_FILE |
+ LANDLOCK_ACCESS_FS_WRITE_FILE,
+ },
+ {
+ .path = file1_s1d2,
+ .access = LANDLOCK_ACCESS_FS_TRUNCATE,
+ },
+ {
+ .path = dir_s2d3,
+ .access = LANDLOCK_ACCESS_FS_TRUNCATE,
+ },
+ // Implicitly: No access rights for file2_s1d1.
+ {},
+ };
+ const int ruleset_fd = create_ruleset(_metadata, ACCESS_ALL, rules);
+ int reg_fd;
+
+ ASSERT_LE(0, ruleset_fd);
+ enforce_ruleset(_metadata, ruleset_fd);
+ ASSERT_EQ(0, close(ruleset_fd));
+
+ /* Read, write and truncate permissions => truncate and ftruncate work. */
+ reg_fd = open(file1_s1d1, O_RDWR | O_CLOEXEC);
+ ASSERT_LE(0, reg_fd);
+ EXPECT_EQ(0, ftruncate(reg_fd, 10));
+ EXPECT_EQ(0, ftruncate64(reg_fd, 20));
+ ASSERT_EQ(0, close(reg_fd));
+
+ EXPECT_EQ(0, truncate(file1_s1d1, 10));
+ EXPECT_EQ(0, truncate64(file1_s1d1, 20));
+
+ /* Just read and write permissions => no truncate variant works. */
+ reg_fd = open(file2_s1d2, O_RDWR | O_CLOEXEC);
+ ASSERT_LE(0, reg_fd);
+ EXPECT_EQ(-1, ftruncate(reg_fd, 10));
+ EXPECT_EQ(EACCES, errno);
+ EXPECT_EQ(-1, ftruncate64(reg_fd, 20));
+ EXPECT_EQ(EACCES, errno);
+ ASSERT_EQ(0, close(reg_fd));
+
+ EXPECT_EQ(-1, truncate(file2_s1d2, 10));
+ EXPECT_EQ(EACCES, errno);
+ EXPECT_EQ(-1, truncate64(file2_s1d2, 20));
+ EXPECT_EQ(EACCES, errno);
+
+ /* Just truncate permissions => truncate(64) works, but can't open file. */
+ ASSERT_EQ(-1, open(file1_s1d2, O_RDWR | O_CLOEXEC));
+ ASSERT_EQ(EACCES, errno);
+
+ EXPECT_EQ(0, truncate(file1_s1d2, 10));
+ EXPECT_EQ(0, truncate64(file1_s1d2, 20));
+
+ /* Just truncate permission on directory => truncate(64) works, but can't open file. */
+ ASSERT_EQ(-1, open(file1_s2d3, O_RDWR | O_CLOEXEC));
+ ASSERT_EQ(EACCES, errno);
+
+ EXPECT_EQ(0, truncate(file1_s2d3, 10));
+ EXPECT_EQ(0, truncate64(file1_s2d3, 20));
+
+ /* No permissions => Neither truncate nor ftruncate work. */
+ ASSERT_EQ(-1, open(file2_s1d1, O_RDWR | O_CLOEXEC));
+ ASSERT_EQ(EACCES, errno);
+
+ EXPECT_EQ(-1, truncate(file2_s1d1, 10));
+ EXPECT_EQ(EACCES, errno);
+ EXPECT_EQ(-1, truncate64(file2_s1d1, 20));
+ EXPECT_EQ(EACCES, errno);
+}
+
static void
reparent_exdev_layers_enforce1(struct __test_metadata *const _metadata)
{
--
2.37.0
next prev parent reply other threads:[~2022-07-07 20:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 20:06 [PATCH 0/2] landlock: truncate(2) support Günther Noack
2022-07-07 20:06 ` [PATCH 1/2] landlock: Support truncate(2) Günther Noack
2022-07-08 11:17 ` Mickaël Salaün
2022-07-10 10:02 ` Günther Noack
2022-07-07 20:06 ` Günther Noack [this message]
2022-07-08 11:17 ` [PATCH 2/2] landlock: Selftests for truncate(2) support Mickaël Salaün
2022-07-11 16:27 ` Günther Noack
2022-07-29 11:30 ` Mickaël Salaün
2022-08-04 16:12 ` Günther Noack
2022-07-08 11:16 ` [PATCH 0/2] landlock: " Mickaël Salaün
2022-07-10 9:57 ` Günther Noack
2022-07-29 11:58 ` Mickaël Salaün
2022-08-04 16:10 ` Günther Noack
2022-08-05 16:52 ` Landlock best-effort Mickaël Salaün
2022-08-05 17:12 ` [PATCH 0/2] landlock: truncate(2) support Mickaël Salaün
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=20220707200612.132705-3-gnoack3000@gmail.com \
--to=gnoack3000@gmail.com \
--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).