summaryrefslogtreecommitdiff
path: root/src/network/networkd-bridge-mdb.c
Commit message (Collapse)AuthorAgeFilesLines
* network/bridge: drop if_bridge.h from bridge.hYu Watanabe2021-11-091-0/+1
| | | | To avoid future header conflicts.
* network: introduce KeepMaster= settingYu Watanabe2021-09-041-10/+0
| | | | Closes #20624.
* network: use master ifindex to check if the interface is enslavedYu Watanabe2021-09-041-27/+9
|
* Drop the text argument from assert_not_reached()Zbigniew Jędrzejewski-Szmek2021-08-031-1/+1
| | | | | | | | | | | | | | | | | In general we almost never hit those asserts in production code, so users see them very rarely, if ever. But either way, we just need something that users can pass to the developers. We have quite a few of those asserts, and some have fairly nice messages, but many are like "WTF?" or "???" or "unexpected something". The error that is printed includes the file location, and function name. In almost all functions there's at most one assert, so the function name alone is enough to identify the failure for a developer. So we don't get much extra from the message, and we might just as well drop them. Dropping them makes our code a tiny bit smaller, and most importantly, improves development experience by making it easy to insert such an assert in the code without thinking how to phrase the argument.
* network: rename Manager::links -> Manager::links_by_indexYu Watanabe2021-07-011-1/+1
| | | | This also renames link_get() -> link_get_by_index().
* network: do not process requests which conditionalized with link flags while ↵Yu Watanabe2021-06-091-0/+3
| | | | | | | | the flags are updating E.g. nexthop requires IFF_UP flag, but the currently stored flag may be outdated if we called link_down(). This makes such requests pending if at least one of the flags are updating.
* network: use request queue to configure bridge MDBYu Watanabe2021-06-081-42/+68
|
* network: rename MdbEntry -> BridgeMDBYu Watanabe2021-06-081-0/+368