diff options
| author | Dmitry Vyukov <[email protected]> | 2025-05-21 15:04:29 +0000 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2025-06-13 16:36:39 +0000 |
| commit | a2fc422ed75748eef2985454e97847fb22f873c2 (patch) | |
| tree | 811388d91b3d50b1b65b3b7230174de8a36448ce /fs/btrfs/tree-mod-log.c | |
| parent | selftests: Fix errno checking in syscall_user_dispatch test (diff) | |
| download | kernel-a2fc422ed75748eef2985454e97847fb22f873c2.tar.gz kernel-a2fc422ed75748eef2985454e97847fb22f873c2.zip | |
syscall_user_dispatch: Add PR_SYS_DISPATCH_INCLUSIVE_ON
There are two possible scenarios for syscall filtering:
- having a trusted/allowed range of PCs, and intercepting everything else
- or the opposite: a single untrusted/intercepted range and allowing
everything else (this is relevant for any kind of sandboxing scenario,
or monitoring behavior of a single library)
The current API only allows the former use case due to allowed
range wrap-around check. Add PR_SYS_DISPATCH_INCLUSIVE_ON that
enables the second use case.
Add PR_SYS_DISPATCH_EXCLUSIVE_ON alias for PR_SYS_DISPATCH_ON
to make it clear how it's different from the new
PR_SYS_DISPATCH_INCLUSIVE_ON.
Signed-off-by: Dmitry Vyukov <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Link: https://lore.kernel.org/all/97947cc8e205ff49675826d7b0327ef2e2c66eea.1747839857.git.dvyukov@google.com
Diffstat (limited to 'fs/btrfs/tree-mod-log.c')
0 files changed, 0 insertions, 0 deletions