Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1358337
| From | Oleg Nesterov <oleg@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH 0/2] wait/ptrace: assume __WALL if the child is traced |
| Date | 2016-03-16 00:40 +0100 |
| Message-ID | <rd6Jb-EH-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Resend. And sorry for the huge delay. The patches are the same, I only updated the changelog a little bit. The previous discussion was a bit confusing, but iirc/iiuc nobody really argued with this change. In particular strace/gdb maintainers do not think it can break something. To remind, 1 and 2 do not depend on each other. But if we decide to not fix the kernel, then 2/2 makes much more sense. Most init's use waitid() which doesn't allow __WALL, so the user-space fix will be more complicated without this patch. And just in case let me repeat that I agree, PTRACE_TRACEME is ugly. And probably it should not succeed after re-parenting (in fact I personally think PTRACE_TRACEME should not even exist). But imho it is too late to try change this ancient interface, at least I strongly dislike the idea to add something like is_global_init() check into ptrace_traceme(). And any "sane" restriction here can break something too, plus this will complicate the rules. Oleg.
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
[PATCH 0/2] wait/ptrace: assume __WALL if the child is traced Oleg Nesterov <oleg@redhat.com> - 2016-03-16 00:40 +0100 [PATCH 1/2] wait/ptrace: assume __WALL if the child is traced Oleg Nesterov <oleg@redhat.com> - 2016-03-16 00:40 +0100 [PATCH 2/2] wait: allow sys_waitid() to accept __WNOTHREAD/__WCLONE/__WALL Oleg Nesterov <oleg@redhat.com> - 2016-03-16 00:40 +0100
csiph-web