From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Stancek <jstancek@redhat.com>
Subject: [bug] child processes stall forever and don't get killed
Date: Fri, 9 Sep 2016 06:30:16 -0400 (EDT)
Message-ID: <210078090.1267922.1473417016250.JavaMail.zimbra@redhat.com>
References: <1139550397.1201862.1473415639192.JavaMail.zimbra@redhat.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <trinity-owner@vger.kernel.org>
In-Reply-To: <1139550397.1201862.1473415639192.JavaMail.zimbra@redhat.com>
Sender: trinity-owner@vger.kernel.org
List-ID: <trinity.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: trinity@vger.kernel.org
Cc: jstancek@redhat.com, davej@codemonkey.org.uk

Hi,

I'm running v1.6-643-gecea2b06d5f3 on RHEL7.3 and I'm seeing an issue
where all child processes stall and none of them is getting killed.
They are usually in a syscalls like read, recv, nanosleep, etc.

I suspect this commit introduced the problem, because any syscall
that started but not completed is now considered to "make progress":

  commit ecf6dfd83d4c886d78d4605163cb8c3f1728db62
  Author: Dave Jones <davej@codemonkey.org.uk>
  Date:   Fri Aug 12 15:05:01 2016 -0400

    if we haven't done a syscall yet, treat child as "making progress".
    
    Chances are that we haven't been scheduled because some other
    children are hogging the cpu.

I'm seeing more the opposite of what commit above says. Most CPUs
are idle, because N-1 children are stuck in recv/read/...
and last child manages to keep going. Then by a chance it also hits
a syscall that doesn't complete and system stays idle
(after ~hour I gave up waiting).

Regards,
Jan