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
Unknown Object (File)
Sat, Sep 5, 6:25 PM
Unknown Object (File)
Sat, Sep 5, 12:01 PM
Unknown Object (File)
Sat, Sep 5, 8:56 AM
Unknown Object (File)
Fri, Sep 4, 9:38 AM
Unknown Object (File)
Thu, Sep 3, 2:48 PM
Unknown Object (File)
Wed, Sep 2, 4:21 AM
Unknown Object (File)
Wed, Sep 2, 3:20 AM
Unknown Object (File)
Tue, Sep 1, 2:48 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