[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151020171740.GA29290@redhat.com>
Date: Tue, 20 Oct 2015 19:17:40 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Dmitry Vyukov <dvyukov@...gle.com>
Cc: Alexander Potapenko <glider@...gle.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Jan Kratochvil <jan.kratochvil@...hat.com>,
Julien Tinnes <jln@...gle.com>,
Kees Cook <keescook@...gle.com>,
Kostya Serebryany <kcc@...gle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
Pedro Alves <palves@...hat.com>,
Robert Swiecki <swiecki@...gle.com>,
Roland McGrath <roland@...k.frob.com>,
syzkaller@...glegroups.com, linux-kernel@...r.kernel.org
Subject: [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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists