From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
jan.kratochvil@redhat.com, palves@redhat.com,
Roland McGrath <roland@hack.frob.com>,
syzkaller <syzkaller@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Unkillable processes due to PTRACE_TRACEME again
Date: Fri, 2 Dec 2016 22:02:17 +0100 [thread overview]
Message-ID: <20161202210217.GA15126@amd> (raw)
In-Reply-To: <CACT4Y+ZnT3ngSvbs=U8=41TAMpaS8YqbVb7KdiK9QTM7Jd+JgA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Fri 2016-12-02 19:48:40, Dmitry Vyukov wrote:
> Hello,
>
> There was an issue discussed a year ago which leads to
> unkillalble/unwaitable zombie processes due to PTRACE_TRACEME:
> https://groups.google.com/d/msg/syzkaller/uGzwvhlCXAw/E-cfY2ejAgAJ
> and I though it has been fixed by "wait/ptrace: assume __WALL if the
> child is traced":
> https://groups.google.com/d/msg/syzkaller/caeB1ebZWAs/gcbvcM2HDAAJ
>
> I am not on 2caceb3294a78c389b462e7e236a4e744a53a474 (Dec 1). And see
"Now on"?
> the same unwaitable zombie processes.
Well.. I guess git bisect is one option...?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-12-02 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 18:48 Unkillable processes due to PTRACE_TRACEME again Dmitry Vyukov
2016-12-02 21:02 ` Pavel Machek [this message]
2016-12-03 15:55 ` Dmitry Vyukov
2016-12-03 19:11 ` Pavel Machek
2016-12-05 10:46 ` Oleg Nesterov
2016-12-05 11:00 ` Oleg Nesterov
2016-12-05 14:07 ` Dmitry Vyukov
2016-12-05 16:59 ` Oleg Nesterov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161202210217.GA15126@amd \
--to=pavel@ucw.cz \
--cc=dvlasenk@redhat.com \
--cc=dvyukov@google.com \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=palves@redhat.com \
--cc=roland@hack.frob.com \
--cc=syzkaller@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).