Skip to content

wait/ptrace: always assume __WALL if the child is traced

Oleg Nesterov lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 18 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2wait/ptrace: always assume __WALL if the child is tracedkernel/exit.c+20 -915 replies
2/2wait: allow sys_waitid() to use __WNOTHREAD/__WCLONE/__WALLkernel/exit.c+2 -10 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] wait/ptrace: always assume __WALL if the child is traced

Damn. I simply do not know what should/can we do. From the change log:

And I can only hope that this won't break something.

yet this patch cc's -stable.

Please see the changelog, but in short: this is not a kernel bug but unlikely we can fix all distributions, so I think we have to change the kernel.

HOWEVER. With this change __WCLONE and __WALL have no effect for debugger, do_wait() works as if __WALL is set if the child (natural or not) is traced.

Jan, Pedro, could you please confirm this won't break gdb? I tried to look into gdb-7.1, and at first glance gdb uses __WCLONE only because __WALL doesn't work on older kernels, iow it seems to me that gdb actually wants __WALL so this change should be fine.

Any other ideas?

Oleg.