[Bug 279850] wireguard: wg(8) fails on INET6-only kernel

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

--- Comment #5 from Lexi Winter <[email protected]> ---
already discussed this with Kevin^W Kyle on IRC, but for completeness, the
patch in comment #1 panics on boot on a system with tunnels configured:

Created clone interfaces: wg0 wg1 epair0a epair0b.
lo0: link state changed to UP
xn0: 2 link states coalesced
xn0: link state changed to UP


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 02
fault virtual address   = 0x0
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xffffffff81e2a57f
stack pointer           = 0x28:0xfffffe0079d73a70
frame pointer           = 0x28:0xfffffe0079d73a80
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 331 (wg)
rdi: fffff80021e5d4d8 rsi: fffff80036b02800 rdx: fffff80021f46c48
rcx: 0000000000000000  r8: fffff800074c8000  r9: 000000000000003a
rax: 0000000000000000 rbx: fffff80036b02800 rbp: fffffe0079d73a80
r10: 0000000000000000 r11: 0000000000000003 r12: fffff80036441c10
r13: fffff80021f4e1c0 r14: fffff80021f46c00 r15: 000000000000002f
trap number             = 12
panic: page fault
cpuid = 1
time = 1725643323
KDB: stack backtrace:
#0 0xffffffff8045dccd at kdb_backtrace+0x5d
#1 0xffffffff80413b5f at vpanic+0x13f
#2 0xffffffff80413a13 at panic+0x43
#3 0xffffffff806954cb at trap_fatal+0x40b
#4 0xffffffff80695516 at trap_pfault+0x46
#5 0xffffffff8066c0f8 at calltrap+0x8
#6 0xffffffff81e284f1 at wg_ioctl+0x1531
#7 0xffffffff8051eed8 at ifioctl+0xd18
#8 0xffffffff8047f555 at kern_ioctl+0x255
#9 0xffffffff8047f29a at sys_ioctl+0x10a
#10 0xffffffff80695d85 at amd64_syscall+0x115
#11 0xffffffff8066ca0b at fast_syscall_common+0xf8
Uptime: 5s
Dumping 338 out of 6119 MB:..5%..15%..24%..34%..43%..53%..62%..71%..81%..95%
Dump complete

-- 
You are receiving this mail because:
You are on the CC list for the bug.