Page MenuHomeFreeBSD

bridge tests: Test for #216510
ClosedPublic

Authored by kp on Apr 1 2020, 2:26 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Dec 19, 6:23 PM
Unknown Object (File)
Nov 24 2024, 10:34 PM
Unknown Object (File)
Nov 24 2024, 10:03 AM
Unknown Object (File)
Nov 23 2024, 2:12 AM
Unknown Object (File)
Nov 22 2024, 2:31 PM
Unknown Object (File)
Nov 19 2024, 9:43 AM
Unknown Object (File)
Nov 12 2024, 5:32 AM
Unknown Object (File)
Nov 12 2024, 5:07 AM
Subscribers

Details

Summary

We used to have an issue with recursive locking with
net.link.bridge.inherit_mac. This causes us to send an ARP request while
we hold the BRIDGE_LOCK, which used to cause us to acquire the
BRIDGE_LOCK again. We can't re-acquire it, so this caused a panic.

Now that we no longer need to acquire the BRIDGE_LOCK for
bridge_transmit() this should no longer panic. Test this.

PR: 216510
Sponsored by: The FreeBSD Foundation

Diff Detail

Lint
Lint Warnings
SeverityLocationCodeMessage
Warningtests/sys/net/if_bridge_test.sh:CHMOD1Invalid Executable
Unit
No Test Coverage
Build Status
Buildable 30230
Build 28015: arc lint + arc unit

Event Timeline

LGTM

tests/sys/net/if_bridge_test.sh
251

Is this a standard way we reference PRs in tests? I'd probably expect PR216510

This revision is now accepted and ready to land.Apr 1 2020, 2:42 PM

Thanks for the review. This can't be committed until the lock rework of the bridge is pushed, because without it this will trigger a recursive lock of BRIDGE_LOCK and panic.

tests/sys/net/if_bridge_test.sh
251

I don't know if we have a standard way of doing this. There are a couple more that use #12345, but those are mostly mine.

There's also a few 'PR 123456' and at least one 'PR kern/123456'.

This looks good. Thank you for adding more tests!

This revision was landed with ongoing or failed builds.Apr 26 2020, 4:27 PM
Closed by commit rS360346: bridge tests: Test for #216510 (authored by kp). · Explain Why
This revision was automatically updated to reflect the committed changes.