Alex/kaido-core
SHA256
Watch
1
0
Fork
You've already forked kaido-core
 0
Code Issues 11 Pull requests 1 Releases Activity Actions

QoS ifb device remains after a restart during activation #86

New issue
Open
opened 2026-11-08 13:28:04 +01:00 by Alex · 0 comments
Alex commented 2026-11-08 13:28:04 +01:00
Owner

Problem

  • A restart while a QoS activation is running can leave its ifb device behind (internal/service/qos_transition.go:365, internal/service/qos.go:206).

Impact

  • The leftover device stays in the kernel and is not tracked by the next activation.

Proposed change

  • Detect and remove leftover agent ifb devices when QoS is applied after a restart.

Validation

  • Kernel test in an isolated network namespace: interrupted activation followed by a restart.
## Problem - A restart while a QoS activation is running can leave its ifb device behind (`internal/service/qos_transition.go:365`, `internal/service/qos.go:206`). ## Impact - The leftover device stays in the kernel and is not tracked by the next activation. ## Proposed change - Detect and remove leftover agent ifb devices when QoS is applied after a restart. ## Validation - Kernel test in an isolated network namespace: interrupted activation followed by a restart.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
134-reply-to-before-routing
119-example-firstboot
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Alex/kaido-core#86
No description provided.