Actions
Bug #3320
closed
vtnet: Panic when setting MTU to 16384
Description
As reported here , a kernel panic is triggered when trying to set MTU to 16384 for vtnet:
root@buildlet:~ # ifconfig vtnet0 mtu 16384
panic: overflowed mbuf 0xfffff8037c5bec00
cpuid = 8
Trace beginning at frame 0xfffff8037cf9c6e8
m_free() at m_free+0x351 0xffffffff806be5c1
m_free() at m_free+0x351 0xffffffff806be5c1
m_freem() at m_freem+0x15 0xffffffff806be845
vtnet_newbuf() at vtnet_newbuf+0x4b 0xffffffff80a71e9b
vtnet_init() at vtnet_init+0x108 0xffffffff80a73848
vtnet_ioctl() at vtnet_ioctl+0x213 0xffffffff80a73d23
Debugger("panic")
CPU8 stopping CPUs: 0x0000feff
stopped
Stopped at Debugger+0x7c: movb $0,0xbcc819(%rip)
db>
db>
Updated by daftaupe almost 2 years ago
I haven't tried yet, but does that panic also happen when changing the MTU on a network interface backed by another driver ?
Updated by daftaupe almost 2 years ago
- Status changed from New to Resolved
@tuxillo, this has just been fixed by dillon in https://bugs.dragonflybsd.org/projects/dragonfly/repository/dragonflybsd/revisions/20bf50996e30140ca0d813694090469045bba0c4h
Updated by daftaupe almost 2 years ago
I did mention the commit in golang's github issue too.
Actions