From owner-freebsd-threads@FreeBSD.ORG  Sun Jun 21 06:31:11 2015
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C8C77BAD
 for <freebsd-threads@hub.freebsd.org>; Sun, 21 Jun 2015 06:31:11 +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 B2398157
 for <freebsd-threads@FreeBSD.org>; Sun, 21 Jun 2015 06:31:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5L6VBZi042697
 for <freebsd-threads@FreeBSD.org>; Sun, 21 Jun 2015 06:31:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 200992] proccess won't die in thread_suspend_switch
Date: Sun, 21 Jun 2015 06:31:11 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-200992-16-aZQoU8wA1G@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200992-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-200992-16@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads/>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jun 2015 06:31:11 -0000

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

Konstantin Belousov <kib@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rrs@FreeBSD.org

--- Comment #4 from Konstantin Belousov <kib@FreeBSD.org> ---
The issue is that callout_stop() call in the sleepq_check_timeout() returned
zero, which made the thread to (in)voluntarily relinguish the CPU.  But
apparently the thread sleep callout was not really run, which means that there
is nobody to make the thread runnable again.

The situation was already fixed once, it is the reason for the
CALLOUT_DFRMIGRATION existence.

For me, it looks as if the r278469 could be a cause.  The added block which
calculates the not_on_a_list means that sometimes previously pending callout is
not longer pending, but also that we return 0 in this case.I think that in case
not_on_a_list == 1, we _must_ return 1 from callout_stop().

I am attaching the non-tested proof of concept patch to try.

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