xenbus: Avoid deadlock during suspend due to open transactions

Bug #1845033 reported by Doug Goldstein
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
Xenial
New
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned
Disco
Fix Released
Undecided
Unassigned
Eoan
Fix Released
Undecided
Unassigned

Bug Description

[Impact]
Xen guests may hang during resume after a migration or suspend.

[Test Case]
Create a Xen guest and run this script and then suspending the VM:

    import pyxs, time
    c = pyxs.client.Client(xen_bus_path="/dev/xen/xenbus")
    c.connect()
    c.transaction()
    time.sleep(3600)

[Fix]
The following upstream commit fixes the issue:

"xenbus: Avoid deadlock during suspend due to open transactions"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d10e0cc113c9e1b64b5c6e3db37b5c839794f3df

Revision history for this message
Doug Goldstein (cardoe) wrote :

This is fixed in bionic with Ubuntu-4.15.0-59.66. Looking to get this ported into xenial.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1845033

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Bob Ball (bob-ball) wrote :

This is equivalent to 1844421

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Thanks for the bug report, this has been applied to the master-next branch of:
  * Disco - https://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/?h=master-next&id=e156b3ed11e418de90b15389a6af7187ace0184b

It's scheduled to be released on the next SRU cycle,

And the master branch of:
  * Bionic - https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master-next&id=683f56d305988dda311e928fba080edb758c8d13
  * Eoan - https://kernel.ubuntu.com/git/ubuntu/ubuntu-eoan.git/commit/?h=master-next&id=d10e0cc113c9e1b64b5c6e3db37b5c839794f3df

Therefor I will mark this as a duplicate of bug 1840076 to keep track of the release status.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Vincent Fortier (th0ma7) wrote :

Bug entry #1845033 also affects Xenial (16.04) and Trusty (14.04 HWE) v4.4 kernels.
Is it possible to backport the fix to 4.4 kernels as well?
Actually I believe this should have been material for 4.4/4.9 mainline stable trees in the first place.

Relates to following fix:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.2.21&id=d10e0cc113c9e1b64b5c6e3db37b5c839794f3df

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

I have set this bug as "not a duplicate", in order to track the request to have the fix backported to the 4.4 kernels (Xenial and Trusty-hwe ).

Changed in linux (Ubuntu Bionic):
status: New → Fix Released
Changed in linux (Ubuntu Disco):
status: New → Fix Released
Changed in linux (Ubuntu Eoan):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.