Well, it's a bit more subtle than that. Because it were the Chromimum developers which created the feature in the first place.
seccomp was introduced in the Linux kernel because the Chromium developers wanted a good way to reduce the harm Chromium browser processes could do if they got compromised.
Chromium is pretty much the only user of seccomp right now.
(although for example Docker also has support for it, but I don't think it's widely used)
Now Kees Cook who implemented TSYNC for seccomp in the Linux kernel works for Google. The kernel commit even lists his @chromium.org email address.
seccomp was introduced in the Linux kernel because the Chromium developers wanted a good way to reduce the harm Chromium browser processes could do if they got compromised.
Chromium is pretty much the only user of seccomp right now.
(although for example Docker also has support for it, but I don't think it's widely used)
Now Kees Cook who implemented TSYNC for seccomp in the Linux kernel works for Google. The kernel commit even lists his @chromium.org email address.