Date: Wed, 19 Apr 2017 10:47:08 +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-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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218597-8-lcLun6F81k>