From owner-freebsd-bugs@freebsd.org  Thu Aug 17 00:25:02 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 A8305DDD3D3
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 17 Aug 2017 00:25:02 +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 968B176736
 for <freebsd-bugs@FreeBSD.org>; Thu, 17 Aug 2017 00:25:02 +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 v7H0P1UC081138
 for <freebsd-bugs@FreeBSD.org>; Thu, 17 Aug 2017 00:25:02 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: Thu, 17 Aug 2017 00:25:00 +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: jhb@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: jhb@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-218597-8-l2lmjrgXMF@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: Thu, 17 Aug 2017 00:25:02 -0000

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

John Baldwin <jhb@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |In Progress
           Assignee|freebsd-bugs@FreeBSD.org    |jhb@FreeBSD.org

--- Comment #8 from John Baldwin <jhb@FreeBSD.org> ---
FYI, I have a potential fix for this in the middle of a larger patch series=
 I'm
working on to enable  AES-GCM offloading for the OpenSSL /dev/crypto engine=
 and
some other things.  It uses malloc'd per-op buffer.  While concurrent
operations on a session are probably rare, we don't do anything to prevent =
them
currently and this makes them safe.  I also prefer to not muddy the per-ses=
sion
state with per-op state.  The relevant commits are:

https://github.com/freebsd/freebsd/commit/6d93ba89e16b137cca55b377c46430815=
cb68464

along with 3 followup fixes in this branch:

https://github.com/freebsd/freebsd/compare/master...bsdjhb:openssl_engine

I don't have an ETA for when this might reach HEAD apart from "soon-ish".  I
have some other open reviews for /dev/crypto changes that I haven't been ab=
le
to get any review for already.

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