Page MenuHomeFreeBSD

rtsock: quiet -Wunused-variable in LINT-NOIP kernels
ClosedPublic

Authored by rlibby on Dec 22 2020, 7:05 PM.
Tags
None
Referenced Files
F80151375: D27730.diff
Thu, Mar 28, 2:43 PM
Unknown Object (File)
Jan 10 2024, 1:54 AM
Unknown Object (File)
Jan 7 2024, 9:56 PM
Unknown Object (File)
Dec 12 2023, 12:09 PM
Unknown Object (File)
Nov 2 2023, 12:21 PM
Unknown Object (File)
Sep 16 2023, 8:41 PM
Unknown Object (File)
Sep 16 2023, 8:41 PM
Unknown Object (File)
Sep 16 2023, 8:37 PM
Subscribers

Details

Summary

Fixup after r368769.

Test Plan

make tinderbox

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 35627
Build 32522: arc lint + arc unit

Event Timeline

Ty for fixing this!

Btw, I'm not sure what's the usecase for NOIP kernels - do we have to have rtsock there at all?
rtsock is (currently) used to control routes/IP/arp/nd records & dump 80211 data, multicast and interface stats.

Is interface data (getifaddrs()) the only actually usable thing there on am I missing something?

This revision is now accepted and ready to land.Dec 22 2020, 7:39 PM

Ty for fixing this!

Sure, no problem, I've been working build issues lately.

Btw, I'm not sure what's the usecase for NOIP kernels - do we have to have rtsock there at all?
rtsock is (currently) used to control routes/IP/arp/nd records & dump 80211 data, multicast and interface stats.

Is interface data (getifaddrs()) the only actually usable thing there on am I missing something?

Unfortunately I really don't know for sure...

It may be more graceful to have the rtsock interfaces and sysctls exist and return empty lists instead of go missing, or maybe it really wouldn't matter in a WITHOUT_INET / WITHOUT_INET6 build. I think making the rtsock.c build optional would be straightforward if we wanted that: optional inet | inet6 instead of standard.