forked from lix-project/lix
alois31
e7188e211a
Unfortunately, io_uring is totally opaque to seccomp, and while currently there
are no dangerous operations implemented, there is no guarantee that it remains
this way. This means that io_uring should be blocked entirely to ensure that
the sandbox is future-proof. This has not been observed to cause issues in
practice.
Change-Id:
|
||
---|---|---|
.. | ||
.gitkeep | ||
ban-integer-overflow.md | ||
better-attrpath-errors.md | ||
block-io-uring.md | ||
build-dir.md | ||
distinguish-throw-errors.md | ||
fix-gc-dry-run.md | ||
fod-failure-includes-url.md | ||
multiline-log-format.md | ||
nix-copy-is-fast.md | ||
old-protocol-removal.md | ||
pretty-printing.md | ||
registry-add-shorthand-only.md | ||
reject-flake-config.md | ||
repl-complete-colon.md | ||
sanitizers.md |