Date: Thu, 17 Aug 2017 00:25:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 218597] [CRYPTODEV] spurious wakeup and synchronisation problem 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218597-8-l2lmjrgXMF>