-
Notifications
You must be signed in to change notification settings - Fork 236
Ubuntu 18.04 Seccomp Failures #197
Comments
Thanks for the report! If you have the time/inclination, could you run stenotype with --seccomp=trace under strace, so we can see if we can find the exact syscall that's causing this issue? I'll also test locally, since I think I may have access to a recent ubuntu on a box somewhere. |
My guess is that some of the flags here changed: https://github.com/google/stenographer/blob/master/stenotype/stenotype.cc#L371 |
It looks that way...
|
Thanks a ton for following up on this! Unfortunately, it appears that the failure occurred not in the main thread, and strace by default only traces the main thread. Would it be possible to rerun this with the |
Sure!
|
Thanks for the fast reply! Here's the offending line: [pid 21230] openat(AT_FDCWD, "/opt/steno/pkts1/PKT0/.1548181425192669", O_WRONLY|O_CREAT|O_DSYNC|O_DIRECT, 0600) = -1 ENOSYS (Function not implemented) It appears that it switched from open() calling the 'open' syscall to calling the 'openat' syscall :( Should have a fix out soon! |
Awesome! Thanks for the help. I'm FAR from a seccomp expert, so you figured this out way faster than I would have. |
Would you mind trying out #201 locally on your instance to see if it fixes the issue? |
I'll get it installed and start it testing shortly. |
Doesn't look like it has done the trick. I put your branch in the place of the standard 'google' one in my GOPATH and ran
|
I can confirm that #201 is not working for me. However, when I added
to the |
It looks like Stenotype's seccomp sandbox may need tweaked for the version of libc that ships with Ubuntu 18.04. For now, those using 18.04 may need to run with
--seccomp=none
.The text was updated successfully, but these errors were encountered: