https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
Roman Bogorodskiy changed:
What|Removed |Added
Status|New |In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
--- Comment #16 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Sat May 14 06:07:15 UTC 2016
New revision: 299725
URL: https://svnweb.freebsd.org/changeset/base/299725
Log:
vtnet: fix panic on unload
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
Roman Bogorodskiy changed:
What|Removed |Added
Attachment #170229|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
--- Comment #11 from Kristof Provost ---
I *think* cxgbe is wrong (or overly cautious). I'd propose doing it without the
mutex in vtnet.
You're not going to make things any worse than the currently are by not adding
it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
--- Comment #13 from Kristof Provost ---
Hmm, can you verify that uma_zdestroy() still gets called?
I think the order is MOD_LOAD on load, but an unload first gets MOD_QUIESCE and
then MOD_UNLOAD.
That'd mean we do
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
--- Comment #10 from Roman Bogorodskiy ---
(In reply to Kristof Provost from comment #9)
Ah, I think that's right:
https://svnweb.freebsd.org/base/head/sys/kern/kern_module.c?revision=289111=markup#l260
It's not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
--- Comment #9 from Kristof Provost ---
That looks correct to me, although I'm not sure if the mutex is actually
required.
The code calling the module load/unload function seems to do so with Giant
held.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
Roman Bogorodskiy changed:
What|Removed |Added
Attachment #170217|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
Roman Bogorodskiy changed:
What|Removed |Added
Attachment #170182|0 |1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428
Kristof Provost changed:
What|Removed |Added
CC|
10 matches
Mail list logo