From owner-freebsd-bugs@freebsd.org  Tue Nov 21 09:53:27 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 168C0DE9477
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 21 Nov 2017 09:53:27 +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 mx1.freebsd.org (Postfix) with ESMTPS id 04B4467465
 for <freebsd-bugs@FreeBSD.org>; Tue, 21 Nov 2017 09:53:27 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAL9rQYV090696
 for <freebsd-bugs@FreeBSD.org>; Tue, 21 Nov 2017 09:53:26 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 223745] PROC_REAP_KILL misses descendants if another process
 has become a reaper in between
Date: Tue, 21 Nov 2017 09:53:26 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-223745-8-UFLj3BgbTl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223745-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-223745-8@https.bugs.freebsd.org/bugzilla/>
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.25
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Nov 2017 09:53:27 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223745

--- Comment #1 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Michael Zuo from comment #0)
Perhaps yes, this might be a reasonable mode of operation.  I am interested=
 on
the bapt@ opinion whether the current mode is useless or should be preserve=
d.

That said, implementing the descent into the descendants of the subordinate
reapers is somewhat clumsy, most likely proctree lock would need to be taken
exclusive to allow marking the processes for tree traversal.

--=20
You are receiving this mail because:
You are the assignee for the bug.=