From: "Günther Noack" <email@example.com>
Cc: "Mickaël Salaün" <firstname.lastname@example.org>,
"James Morris" <email@example.com>,
"Paul Moore" <firstname.lastname@example.org>,
"Serge E . Hallyn" <email@example.com>,
"Günther Noack" <firstname.lastname@example.org>
Subject: [PATCH v4 0/4] landlock: truncate support
Date: Sun, 14 Aug 2022 21:25:59 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
The goal of these patches is to work towards a more complete coverage
of file system operations that are restrictable with Landlock.
The known set of currently unsupported file system operations in
Landlock is described at . Out of the operations listed there,
truncate is the only one that modifies file contents, so these patches
should make it possible to prevent the direct modification of file
contents with Landlock.
The patch introduces the truncation restriction feature as an
additional bit in the access_mask_t bitmap, in line with the existing
The truncation flag covers both the truncate(2) and ftruncate(2)
families of syscalls, as well as open(2) with the O_TRUNC flag.
This includes usages of creat() in the case where existing regular
files are overwritten.
Apart from Landlock, file truncation can also be restricted using
seccomp-bpf, but it is more difficult to use (requires BPF, requires
keeping up-to-date syscall lists) and it is not configurable by file
hierarchy, as Landlock is. The simplicity and flexibility of the
Landlock approach makes it worthwhile adding.
While it's possible to use the "write file" and "truncate" rights
independent of each other, it simplifies the mental model for
userspace callers to always use them together.
Specifically, the following behaviours might be surprising for users
when using these independently:
* The commonly creat() syscall requires the truncate right when
overwriting existing files, as it is equivalent to open(2) with
* The "write file" right is not always required to truncate a file,
even through the open(2) syscall (when using O_RDONLY|O_TRUNC).
Nevertheless, keeping the two flags separate is the correct approach
to guarantee backwards compatibility for existing Landlock users.
These patches are based on version 5.19.
* Clarify wording and syntax as discussed in review.
* Use a less confusing error message in the example.
* Stop using ASSERT_EQ in test helpers, return EBADFD instead.
(This is an intentionally uncommon error code, so that the source
of the error is clear and the test can distinguish test setup
failures from failures in the actual system call under test.)
* Use additional clarifying comments in the kernel backwards
* Explicitly test ftruncate with readonly file descriptors
* Extract test_ftruncate, test_truncate, test_creat helpers,
which simplified the previously mixed usage of EXPECT/ASSERT.
* Test creat() behaviour as part of the big truncation test.
* Stop testing the truncate64(2) and ftruncate64(2) syscalls.
This simplifies the tests a bit. The kernel implementations are the
same as for truncate(2) and ftruncate(2), so there is little benefit
from testing them exhaustively. (We aren't testing all open(2)
* Use switch() to implement best effort mode.
* Give more background on surprising truncation behaviour.
* Use switch() in the example too, to stay in-line with the sample tool.
* Small fixes in header file to address previous comments.
* Fix some typos and const usages.
* Documentation: Mention the truncation flag where needed.
* Documentation: Point out connection between truncation and file writing.
* samples: Add file truncation to the landlock/sandboxer.c sample tool.
* selftests: Exercise open(2) with O_TRUNC and creat(2) exhaustively.
* selftests: Exercise truncation syscalls when the truncate right
is not handled by Landlock.
Günther Noack (4):
landlock: Support file truncation
selftests/landlock: Selftests for file truncation support
samples/landlock: Extend sample tool to support
landlock: Document Landlock's file truncation support
Documentation/userspace-api/landlock.rst | 52 ++++-
include/uapi/linux/landlock.h | 17 +-
samples/landlock/sandboxer.c | 23 +-
security/landlock/fs.c | 9 +-
security/landlock/limits.h | 2 +-
security/landlock/syscalls.c | 2 +-
tools/testing/selftests/landlock/base_test.c | 2 +-
tools/testing/selftests/landlock/fs_test.c | 226 ++++++++++++++++++-
8 files changed, 305 insertions(+), 28 deletions(-)
next reply other threads:[~2022-08-14 19:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 19:25 Günther Noack [this message]
2022-08-14 19:26 ` [PATCH v4 1/4] landlock: Support file truncation Günther Noack
2022-08-16 19:20 ` Mickaël Salaün
2022-08-17 16:31 ` Günther Noack
2022-08-14 19:26 ` [PATCH v4 2/4] selftests/landlock: Selftests for file truncation support Günther Noack
2022-08-16 17:08 ` Mickaël Salaün
2022-08-17 18:00 ` Günther Noack
2022-08-17 19:35 ` Günther Noack
2022-08-18 11:26 ` Mickaël Salaün
2022-08-14 19:26 ` [PATCH v4 3/4] samples/landlock: Extend sample tool to support LANDLOCK_ACCESS_FS_TRUNCATE Günther Noack
2022-08-14 19:26 ` [PATCH v4 4/4] landlock: Document Landlock's file truncation support Günther Noack
2022-08-16 19:18 ` Mickaël Salaün
2022-08-17 18:21 ` Günther Noack
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.