RE: [libattach] misleading error message when checking gid fails

2022-01-07 Thread Kevin Walls
7 January 2022 18:25 To: Baesken, Matthias ; Alan Bateman ; stuart nelson ; serviceability-dev@openjdk.java.net Subject: Re: [libattach] misleading error message when checking gid fails Hi, Just some addition to the below comment. The man page also has this: RATIONALE top

Re: [libattach] misleading error message when checking gid fails

2022-01-07 Thread Serguei Spitsyn
iginal Message- From: jdk-dev On Behalf Of Alan Bateman Sent: Freitag, 7. Januar 2022 12:48 To: stuart nelson ; jdk-...@openjdk.java.net Subject: Re: [libattach] misleading error message when checking gid fails On 07/01/2022 11:33, stuart nelson wrote: > Hey,

RE: [libattach] misleading error message when checking gid fails

2022-01-07 Thread Baesken, Matthias
Of Alan Bateman Sent: Freitag, 7. Januar 2022 12:48 To: stuart nelson ; jdk-...@openjdk.java.net Subject: Re: [libattach] misleading error message when checking gid fails On 07/01/2022 11:33, stuart nelson wrote: > Hey, > > First, apologies if this should be directed to a different mail

Re: [libattach] misleading error message when checking gid fails

2022-01-07 Thread Florian Weimer
* stuart nelson: > The reason getegid() returns -1 is because it wasn't in my allowed > syscalls list for seccomp, so EPERM (-1) was returned instead. Surely that's a broken seccomp filter. Such fundamental system calls really cannot be filtered. Thanks, Florian