Page MenuHomeFreeBSD

ipfw(8): Fix most warnings with the default WARNS level.
ClosedPublic

Authored by markj on Jun 25 2020, 7:25 PM.
Tags
None
Referenced Files
F169120633: D25456.id74411.diff
Mon, Aug 31, 11:40 AM
F169063397: D25456.id73651.diff
Mon, Aug 31, 7:31 AM
Unknown Object (File)
Sun, Aug 30, 9:32 AM
Unknown Object (File)
Sat, Aug 29, 9:30 PM
Unknown Object (File)
Thu, Aug 27, 4:37 AM
Unknown Object (File)
Tue, Aug 25, 9:42 PM
Unknown Object (File)
Tue, Aug 25, 9:05 PM
Unknown Object (File)
Wed, Aug 19, 2:41 PM
Subscribers

Details

Summary

Most of these fall into one of several patterns.


- Missing const qualifiers. All but one of these were benign (i.e.,
adding "const" fixes the warning). The exception was in print_ip(),
where we write

cmd->addr.s_addr = htonl(cmd->addr.s_addr);
<print statement>
cmd->addr.s_addr = htonl(cmd->addr.s_addr);


so this can easily be fixed with a temporary variable.

- A global variable `co` shadowing local declarations. In ipfw2.c, some
code gets `co` through a function parameter for some reason. I
renamed the global `co` to `g_co`. I think this will help a bit if
anyone ever tries to convert this code to a libipfw.

- Using a signed int as an index variable where the loop bound is
unsigned. I just converted the variable to have the same type as the
bound.

- Missing static qualifiers on some functions.

- I left the -Wcast-align warnings alone. They are more involved to
fix. It might be sufficient to just add an __aligned qualifier to the
corresponding kernel types.

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 31962
Build 29512: arc lint + arc unit