vrf: fix refcnt leak with vxlan slaves
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt to drop to 0, with the message:
unregister_
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device used for dst_alloc with local routes"), included in linux v5.13. The original patch, which has introduced the bug, is included in linux v4.10.
https:/
[Test Case]
The upstream patch includes a test case, which describe how to reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new dst to a vrf device instead of the loopback if needed.
CVE References
tags: | added: patch |
Changed in linux (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Bionic): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux (Ubuntu Bionic): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Focal): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Confirmed |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-focal removed: verification-needed-focal |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in linux (Ubuntu): | |
assignee: | nobody → Luke Nowakowski-Krijger (lukenow) |
assignee: | Luke Nowakowski-Krijger (lukenow) → nobody |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1945180
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.