Deferring seccomp decisions to user space
Deferring seccomp decisions to user space
Posted Jun 3, 2018 13:11 UTC (Sun) by jhoblitt (subscriber, #77733)In reply to: Deferring seccomp decisions to user space by brauner
Parent article: Deferring seccomp decisions to user space
Posted Sep 14, 2018 13:32 UTC (Fri)
by mathstuf (subscriber, #69389)
[Link] (1 responses)
To not make this just a snark, I'll add a data point. I've seen git-lfs not want to fork out to Git for things like `remote get-url` and rather re-implement `insteadOf` and `pushInsteadOf` yet again. And so git-lfs is still broken with alias remote URLs that differ in push and pull. Attribute reading is also broken in the case of user "[attr]" attributes. Yes, both have issues filed (and I don't know Go (yet?) well enough to fix it myself).
I believe the *only* thing they fork for is to find out the version of Git used elsewhere. There might be one or two more instances as well, but they're of a similar level of actual functionality sharing.
Posted Sep 14, 2018 14:46 UTC (Fri)
by zlynx (guest, #2285)
[Link]
I do wish that the netlink formats were better documented.
Calling C code from Go causes all sorts of complex interactions with the green threads and garbage collection so it is not a good idea to casually link into CGo.
Deferring seccomp decisions to user space
Deferring seccomp decisions to user space