https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253473
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253469
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
On Fri, Feb 12, 2021 at 4:14 PM Alexander V. Chernikov
wrote:
> The slightly different approach here: https://reviews.freebsd.org/D28629
> We indeed are running under epoch, so that prevents _immediate_ ifa
> destruction.
> However, we still can run into the situation when
> * in thread 1 we drop
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Thanks! For reference, I tried this patch and it did resolve my leak:
https://github.com/rysto32/freebsd/commit/73caa71c351c072d673d477972fda2aeb369eb3d
I haven't exhaustively tested the routing code, though, so I can't say
for certain that the assert will always be true, nor am I certain that
n
On main I'm seeing leaks of ifaddr reference counts. I can reproduce
this in a bhyve VM by repeating this:
vlan=`ifconfig vlan create vlandev vtnet0 vlan 777`
ifconfig $vlan up
ifconfig $vlan 1.0.0.1/24
ifconfig $vlan destroy
If I watch the ifaddr column of vmstat -m
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
