[linux-azure] Request for two CIFS commits in 16.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-azure-4.15 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[Impact]
There was a previous bug requesting the following two commits in 18.04:
84a1f5b1cc6f ("cifs: Fix potential softlockups while refreshing DFS cache")
2084ed57167c ("CIFS: Only send SMB2_NEGOTIATE command on new TCP connections")
There is an issue now, which requires these commits in the 4.15 based 16.04 kernel.
Can these two commits be applied to 16.04?
(Those changes were include to 5.4 via the upstream stable updates previously)
[Test Case]
The issue is hard to reproduce since it is related to issues during reconnects. I will rely on Microsoft to test and also review the changes.
[Regression Potential]
The changes affect only CIFS, so it would only affect linux-azure systems that makes use of CIFS.
CVE References
Changed in linux-azure-4.15 (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in linux-azure-4.15 (Ubuntu): | |
status: | New → Invalid |
no longer affects: | linux-azure (Ubuntu) |
no longer affects: | linux-azure (Ubuntu Xenial) |
no longer affects: | linux-azure (Ubuntu Bionic) |
no longer affects: | linux-azure-4.15 (Ubuntu Xenial) |
Changed in linux-azure-4.15 (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Since bionic: linux-azure- 4.15 is our base 4.15 azure kernel I'm targeting it instead and xenial:linux-azure will receive the changes automatically when rebased on top of bionic: linux-azure- 4.15.