Page MenuHomeFreeBSD

Use the thread's vnet when iterating over interfaces.
ClosedPublic

Authored by markj on May 16 2018, 12:42 AM.
Tags
None
Referenced Files
F144380367: D15449.id42655.diff
Sun, Feb 8, 3:44 AM
F144332401: D15449.id42608.diff
Sat, Feb 7, 9:40 PM
Unknown Object (File)
Fri, Jan 30, 8:38 PM
Unknown Object (File)
Nov 27 2025, 4:49 AM
Unknown Object (File)
Nov 20 2025, 2:52 PM
Unknown Object (File)
Nov 20 2025, 2:51 PM
Unknown Object (File)
Nov 20 2025, 2:50 PM
Unknown Object (File)
Nov 20 2025, 2:44 PM
Subscribers

Details

Summary

For now, only permit the use of interfaces from vnet0; netdump may only
be configured from the host, and it's not clear to me that interface
names are unique across vnets. This fixes a panic when configuring
netdump with VIMAGE enabled.

Also fix a resource leak that occurs if the priv_check() in set_dumper()
or clear_dumper() fails. Note that netdump_mbuf_drain() is idempotent.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable