Hi Joshua,
I will touched base with Gavin to compare our trees. My test kernel is the
current Azure kernel with two commits applied: d633198088bd9 and
eb4c2382272ae7. Commit eb4c2382272ae7 being the patch from
Dennis Krein in linux-next:
eb4c2382272a ("srcu: Lock srcu_data structure in srcu_gp_start()")
Gavin and I both had the same set of commits. I can submit and SRU
request for this if you don't want to wait for the testing, since it
could take a long time. If I submit it this week, it won't land in the
Azure kernel until the next SRU cycle in the new year. Just let us know
what you think.
Here are the dates for the next cycle:
cycle: 14-Jan through 03-Feb
====================================================================
11-Jan Last day for kernel commits for this cycle.
14-Jan - 18-Jan Kernel prep week.
21-Jan - 01-Feb Bug verification & Regression testing.
31-Jan Release 18.04.2 kernels to -updates
04-Feb Release remaining kernels to -updates.
Looking at these dates, we may want to SRU it this week, due to a
Company shutdown between 24-Dec and 06-Jan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802021
Title:
[Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
