zygoon

joined 3 years ago
sorted by: new top controversial old
There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread. in c/[email protected]
[–] [email protected] 1 points 9 months ago (2 children)

@Conan_Kudo @carlschwan @[email protected] @[email protected] yeah, I strongly suspect seccomp. I’m debugging this now and I will share updates when I get to the bottom of the problem.

There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread. in c/[email protected]
[–] [email protected] 0 points 9 months ago (4 children)

@carlschwan @[email protected] @[email protected]

Yeah, RHEL 7 uses it out of the box and is still supported, at least until June 2024: https://www.redhat.com/en/blog/end-maintenance-red-hat-enterprise-linux-7-almost-here

There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread. in c/[email protected]
[–] [email protected] 1 points 9 months ago

@brauner @[email protected] @[email protected]

Thanks for the insight. I was surprised by EPERM, would have expected ENOSYS as well.

Looks like EPERM is most likely coming out of unknow system call name being filtered-out by snap-seccomp compiler. I'll update snapd to 2.61.1 to avoid chasing fixed bugs and then see if there's something to improve in the compiler.

1
There's some mismatch between Linux kernel 3.10 and #KDE that wants to use clone3 to create a process thread. (fosstodon.org)
 

There's some mismatch between Linux kernel 3.10 and #KDE that wants to use clone3 to create a process thread.

Do I know anyone from @[email protected] @[email protected] who is able to assist with debugging it further?

The system call clone3 has been added to linux 5.3 but it seems that KDE does not do any fallback in case the system call is rejected with EPERM.