This is not just a config issue, it is a lack of hooking up SECCOMP thread flag in ARM. I've got a kernel patch that now compiles, but I will need some hand-holding on testing it. As I understood SECCOMP, it is used to restrict access to the syscalls that a process thread can make to the following - read, write, exit and sigreturn.
Do you have a sample program that will allow me to test if other syscalls are being permitted or not? -- CONFIG_SECCOMP missing on ARM https://bugs.launchpad.net/bugs/375183 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
