[linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel
Bug #1821378 reported by
Joseph Salisbury
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-azure (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This is a request to include the following two commits in 16.04 and 18.04 linux-azure:
fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")
Both commits are fixes to prior commits and have been cc'd to upstream stable.
Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4
The problem these commits fix is that some of the code for displaying values for entries in /sys/bus/vmbus don't have appropriate locking to prevent reading an entry while it is being created or being freed. The result is accessing a bogus memory address.
tags: | added: kernel-hyper-v |
Changed in linux-azure (Ubuntu Cosmic): | |
status: | New → Fix Committed |
Changed in linux-azure (Ubuntu Xenial): | |
status: | New → Fix Committed |
To post a comment you must log in.
https:/ /lists. ubuntu. com/archives/ kernel- team/2019- April/100261. html