From owner-freebsd-bugs@freebsd.org  Wed Apr 19 10:47:09 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 88729D45ED3
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 19 Apr 2017 10:47:09 +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 729A51233
 for <freebsd-bugs@FreeBSD.org>; Wed, 19 Apr 2017 10:47:09 +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 v3JAl8VO020636
 for <freebsd-bugs@FreeBSD.org>; Wed, 19 Apr 2017 10:47:09 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 218597] [CRYPTODEV] spurious wakeup and synchronisation problem
Date: Wed, 19 Apr 2017 10:47:08 +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: patch
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-218597-8-lcLun6F81k@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-218597-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-218597-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.23
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: Wed, 19 Apr 2017 10:47:09 -0000

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

--- Comment #6 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Alexandre martins from comment #4)
If you want to use on-stack memory from another thread or from an interrupt
context, be aware that the thread's kstacks are generally swappable.  Of
course, the stack is swapped in when the thread is marked runnable, but
otherwise you may get into a situation when other thread accessing unmapped
kstack.

You may work around this with PHOLD(), but that would keep whole stack in
memory when system desperately needs it.  In other words, using malloc(9) is
less troublesome.

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