6 ms·
Can someone say what TSYNC is? Googling it did not help me, lots of links, but none that said what it actually is.
by ars 12y ago
Can someone say what TSYNC is? Googling it did not help me, lots of links, but none that said what it actually is.
- deleted 12y ago[deleted]
- gst 12y agoThat's another tsync.
- gst 12y agohttps://lwn.net/Articles/603815/ https://lwn.net/Articles/603815/
- nandhp 12y agoIt looks like a "thread-sync" feature for seccomp. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379020 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379020 http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/273472.html http://lists.infradead.org/pipermail/linux-arm-kernel/2014-J... seccomp ("secure computing") is an application sandboxing mechanism in the Linux kernel (since 2.6.12, 2005-03-08). seccomp allows a process to make a one-way transition into a "secure" state where it cannot make any system calls except exit(), sigreturn(), read() and write() to already-open file descriptors. http://en.wikipedia.org/wiki/Seccomp http://en.wikipedia.org/wiki/Seccomp Chrome uses seccomp to sandbox rendering subprocesses and the Adobe Flash Player.
- justincormack 12y agoIt is the seccomp type 2 mechanism, where you choose the system calls and arguments to allow, not the early seccomp type 1 that only allowed exit, read. That one would not really need to sync, as you cannot even create threads afterwards.
- zobzu 12y agoit synchronize all the process's threads to use the same seccomp filter (seccomp being a sandbox mechanism - a bit like a firewall for system calls). Threads on Linux are very close to an equivalent of "separate process" except they share memory. Up to until seccomp tsync, only the thread calling seccomp and it's children would get the seccomp filter. If you wanted to have seccomp in previously started threads you'd have to handle a broadcast in userspace and ensure all threads actually apply the same seccomp filter. I bet they ran into issues with that (it's easy to forget a thread or have a new thread someone elses coded that will fail to apply the filter). tsync is kernel side and explicitly fails/succeeds so its both simpler and safer.