hakurei/helper/seccomp, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/helper/seccomp?h=develop2025-03-14T13:42:40Zseccomp: move out of helper2025-03-14T13:42:40ZOphestracat@gensokyo.uk2025-03-14T13:42:40Zurn:sha1:2647a71be1f287e50011a65653b9e9c806627899
Signed-off-by: Ophestra <cat@gensokyo.uk>
helper/seccomp: improve error handling2025-03-12T06:52:48ZOphestracat@gensokyo.uk2025-03-12T06:52:48Zurn:sha1:29c3f8becb875de308be9238f5ca0ba9f35eb7bd
This passes both errno and libseccomp return value.
Signed-off-by: Ophestra <cat@gensokyo.uk>
helper/seccomp: seccomp_load on negative fd2025-03-12T06:18:52ZOphestracat@gensokyo.uk2025-03-12T06:18:52Zurn:sha1:be16970e770554b3c2191da41eb9bd4472b323e4
Signed-off-by: Ophestra <cat@gensokyo.uk>
fortify: keep external files alive2025-02-22T18:24:37ZOphestracat@gensokyo.uk2025-02-22T18:24:37Zurn:sha1:eda4d612c2e64321766e1074a698caeae843102a
This should eliminate sporadic failures, like the known double close in "seccomp".
Signed-off-by: Ophestra <cat@gensokyo.uk>
fmsg: implement suspend in writer2025-02-16T09:51:53ZOphestracat@gensokyo.uk2025-02-16T08:26:09Zurn:sha1:e599b5583dd821ed26bdfc01f7f67d4a317b9843
This removes the requirement to call fmsg.Exit on every exit path, and enables direct use of the "log" package. However, fmsg.BeforeExit is still encouraged when possible to catch exit on suspended output.
Signed-off-by: Ophestra <cat@gensokyo.uk>
helper: use generic extra files interface2025-02-13T14:34:15ZOphestracat@gensokyo.uk2025-02-13T14:15:34Zurn:sha1:fe7d208cf76fa6f24bb9d12ba29b5ed61d837ce3
This replaces the pipes object and integrates context into helper process lifecycle.
Signed-off-by: Ophestra <cat@gensokyo.uk>
helper/seccomp: use sync.Once for closeWrite2025-02-13T13:49:16ZOphestracat@gensokyo.uk2025-02-13T13:49:16Zurn:sha1:d1d20c06fb0c3ed5aaff15f284921a5e61c291e1
This makes the code much cleaner, and eliminates the intermittent ErrInvalid errors.
Signed-off-by: Ophestra <cat@gensokyo.uk>
helper/seccomp: benchmark exporter2025-02-13T13:37:51ZOphestracat@gensokyo.uk2025-02-13T13:37:51Zurn:sha1:1e6a0596687ee772fd53317727f5724dd119668c
Signed-off-by: Ophestra <cat@gensokyo.uk>
helper/seccomp: eliminate data race on pfd2025-02-13T01:40:51ZOphestracat@gensokyo.uk2025-02-13T01:40:51Zurn:sha1:099da78af5b78ac69a9c3550229a29d8dac0e9f8
Turns out the doc comment on os.File was lying about its methods being safe for concurrent use. The race detector picked up a data race from concurrent use of Fd and Close.
This change eliminates that by calling Fd in the prepare routine.
Signed-off-by: Ophestra <cat@gensokyo.uk>
helper/seccomp: panic on invalid closeWrite use2025-02-07T03:58:20ZOphestracat@gensokyo.uk2025-02-07T03:58:20Zurn:sha1:568d7758d5308457967672997d9d2e786c7403f1
Returning an error here puts exporter in an invalid state. The caller should guard against this condition instead.
Signed-off-by: Ophestra <cat@gensokyo.uk>