veth: Avoid spammy dmesg info messages #17705
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid spamming the kernel log with below messages as reported by @mukeshkwm:
[...]
[Mon Oct 25 06:48:03 2021] cilium_host: Caught tx_queue_len zero misconfig
[Mon Oct 25 06:48:03 2021] cilium_net: Caught tx_queue_len zero misconfig
[Mon Oct 25 06:48:08 2021] lxc_health: Caught tx_queue_len zero misconfig
[...]
[Mon Oct 25 07:22:27 2021] lxc667d091cb0ea: Caught tx_queue_len zero misconfig
[Mon Oct 25 07:22:27 2021] lxc742557edbdd8: Caught tx_queue_len zero misconfig
[Mon Oct 25 07:22:27 2021] lxc_health: Caught tx_queue_len zero misconfig
[Mon Oct 25 07:22:27 2021] lxcb7215aa13fc7: Caught tx_queue_len zero misconfig
[...]
These are harmless and the kernel will internally fix up dev->tx_queue_len
to DEFAULT_TX_QUEUE_LEN (== 1000). Avoid the messages by explicitly setting
the dev->tx_queue_len upon veth creation.
Fixes: #17703
Signed-off-by: Daniel Borkmann daniel@iogearbox.net