[Bug 279738] Hyper-V: Kernel panic: acquiring blockable sleep lock with spinlock or critical section held

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

--- Comment #8 from commit-hook@FreeBSD.org ---
A commit in branch stable/14 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=d56a912f2fb6fb26a00e950a26e420729e6ef775

commit d56a912f2fb6fb26a00e950a26e420729e6ef775
Author:     Wei Hu <whu@FreeBSD.org>
AuthorDate: 2024-06-15 14:07:58 +0000
Commit:     Wei Hu <whu@FreeBSD.org>
CommitDate: 2024-07-01 13:33:08 +0000

    Hyper-V: move memory alloc call for tlb hypercall out of smp_rendezvous

    The allocation call could result in sleep lock violation if it is in
    smp_rendezvous. Move it out. Also move the pcpu memory pointer to
    vmbus_pcpu_data since it is only used on Hyper-V.

    PR:             279738
    Reported by:    gbe
    Fixes:          2b887687edc25bb4553f0d8a1183f454a85d413d
    MFC after:      2 weeks
    Sponsored by:   Microsoft

    (cherry picked from commit d0cb4674df97aa638d5d17861c364b1625f79401)

 sys/dev/hyperv/vmbus/hyperv_mmu.c |  6 +--
 sys/dev/hyperv/vmbus/vmbus.c      | 88 +++++++++++++++++++++++++++++----------
 sys/dev/hyperv/vmbus/vmbus_var.h  |  5 ++-
 3 files changed, 71 insertions(+), 28 deletions(-)

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