From owner-freebsd-bugs@freebsd.org Thu Oct 4 05:45:16 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 813B210C0A7C for ; Thu, 4 Oct 2018 05:45:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1C4A084172 for ; Thu, 4 Oct 2018 05:45:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D29A910C0A7B; Thu, 4 Oct 2018 05:45:15 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97E5810C0A7A for ; Thu, 4 Oct 2018 05:45:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 38D5084171 for ; Thu, 4 Oct 2018 05:45:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 98B1B7C32 for ; Thu, 4 Oct 2018 05:45:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w945jE5r095609 for ; Thu, 4 Oct 2018 05:45:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w945jE0g095605 for bugs@FreeBSD.org; Thu, 4 Oct 2018 05:45:14 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231933] bc hanging and leaving zombie of dc when being called by process with SIGCHLD blocked Date: Thu, 04 Oct 2018 05:45:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: vladimirv@ixsystems.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 05:45:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231933 Bug ID: 231933 Summary: bc hanging and leaving zombie of dc when being called by process with SIGCHLD blocked Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: vladimirv@ixsystems.com Created attachment 197768 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D197768&action= =3Dedit Patch that fixes described issue In our system (http://www.freenas.org/) uwsgi application server calls a py= thon program that calls a shell script that calls a shell script that calls bc a= nd it hangs leaving us with hanging process tree like this: ``` 3135 |-- /usr/local/bin/uwsgi <...long text cut> 4435 | `-- /usr/local/bin/uwsgi <...long text cut> 8952 | |-- /bin/sh /usr/sbin/service smartd-daemon status 9087 | | `-- /bin/sh /usr/sbin/service smartd-daemon status 9088 | | `-- /bin/sh /usr/sbin/service smartd-daemon status 9090 | | `-- /usr/bin/bc 9091 | | `-- ``` This happens because bc relies on SIGCHLD to determine that dc has complete= d, wait for it and exit on it's own. SIGCHLD is blocked by uwsgi and this bloc= king is inherited by each it's subprocess. Our shell scripts are rather complica= ted and call a lot of other programs and bc was the only one that has this issu= e, so, despite no specification defines who should clear process signal mask, caller or callee, I think this should be fixed with simple patch attached. --=20 You are receiving this mail because: You are the assignee for the bug.=