From owner-freebsd-bugs@FreeBSD.ORG  Fri May 29 10:35:23 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D7C84C89
 for <freebsd-bugs@FreeBSD.org>; Fri, 29 May 2015 10:35:23 +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 C19F513C9
 for <freebsd-bugs@FreeBSD.org>; Fri, 29 May 2015 10:35:23 +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 t4TAZNXn014065
 for <freebsd-bugs@FreeBSD.org>; Fri, 29 May 2015 10:35:23 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 200493] Killing pid 11 (idle) wedges the disk IO
Date: Fri, 29 May 2015 10:35:24 +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: 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-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200493-8-BGFGcsuvPi@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200493-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-200493-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2015 10:35:23 -0000

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

--- Comment #8 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Konstantin Belousov from comment #7)
And to express my opinion on the whole stuff.

The signal delivery to the kernel threads must be opt-in feature.  Kernel
thread should explicitely declare the ability to handle signals directed to it.
 E.g., nfsd threads check for signal as an indication of exit request.

Most threads do not handle signals at all, and queuing the signal to them
causes odd side-effects.  Most innocent consequence is the memory leak due to
queued ksiginfo, which is never deleted from the sigqueue.  Or, the priority
bump for the idle thread, as you discovered.

Code to prevent even queuing signals to the kernel threads is trivial, but it
requires careful examination of each call to kproc/kthread creation to decide
should the signalling be allowed.  The patch I provided IMO is good stop-gap
measure which fixes the immediate ugly case.

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