selftests/exec: test the pre-opened interpreter limit

Browse source

- an interpreter opened at registration is charged
- an interpreter a 'B' entry binds is charged too
- an entry that opens none is not
- removing an entry gives the charge back
- a nested user namespace cannot buy itself budget by raising its own limit

Skips where the sysctl or binfmt_misc is missing. The 'B' case lives in
binfmt_misc_bpf.c because binding needs a handler. It binds from a child
in a user namespace of its own, through the fd the child inherited, so
the charge lands on the child while the interpreter is still opened with
the entry file's credentials, and nothing outside the child sees a
changed limit.

Link: https://patch.msgid.link/20260803-work-binfmt_misc-interplimit-v1-2-4a2435500bd9@kernel.org
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>

...

This commit is contained in:

Christian Brauner 2026-08-03 14:15:01 +02:00

parent b604897764

commit f2b69ea2d1

No known key found for this signature in database

GPG key ID: 91C61BC06578DCA2

4 changed files with 309 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

tools/testing/selftests/exec/.gitignore vendored

View file

6

tools/testing/selftests/exec/Makefile

View file

70

tools/testing/selftests/exec/binfmt_misc_bpf.c

View file

232

tools/testing/selftests/exec/binfmt_misc_interplimit.c

View file