[SRU] Handle changing UUID endian-ness on Azure in cloud-init

Bug #1551419 reported by Stephen A. Zarkos on 2016-02-29
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Undecided
Unassigned
Trusty
Undecided
Dan Watkins
Vivid
Undecided
Unassigned
linux (Ubuntu)
Critical
Unassigned
Trusty
Critical
Luis Henriques
Vivid
Critical
Luis Henriques
linux-keystone (Ubuntu)
Undecided
Unassigned
Trusty
Critical
Luis Henriques
Vivid
Undecided
Unassigned
linux-lts-utopic (Ubuntu)
Trusty
Critical
Luis Henriques

Bug Description

On Azure, cloud-init relies on the system-uuid as based by SMBIOS a unique ID for a cloud instance. If this ID ever changes, then cloud-init will attempt to reprovision the VM.

This recent kernel patch in the Ubuntu kernel incorrectly modifies the endianness for some SMBIOS fields, which has the effect causing cloud-init to think that the system-uuid has changed: http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

cloud-init needs to consider both the reported UUID and the "first three fields endian-reversed" UUID as the same, so that users shifting between unaffected kernels and affected kernels, or affected kernels and fixed kernels do not see their instances reprovisioned.

[Impact]

The impact is that cloud-init attempts to reprovision VMs when they reboot to use the new kernel, often causing the customer to lose access to their VM.

Once the kernel is fixed, rebooting from an affected kernel to the new kernel will have the same effect.

[Test Case]

Failure:

1) Boot an Azure instance using an image with a pre-broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
2) Upgrade the kernel and reboot.
3) SSH to the instance; you will observe that you are prompted to change SSH host keys because cloud-init has run again.

Success (upgrade from not broken->broken):

1) Boot an Azure instance using an image with a pre-broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
2) Install the new version of cloud-init.
3) Upgrade the kernel and reboot.
4) Observe that you are not prompted when SSHing to instance, as cloud-init has not run again.
5) Make a note of the instance ID in use (i.e. the target of /var/lib/cloud/instance
6) Reboot again.
7) Observe that the instance ID has not changed.

Success (upgrade from broken->fixed):
1) Boot an Azure instance using an image with a broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
2) Install the new version of cloud-init.
3) Upgrade to the fixed kernel (once it is available) and reboot.
4) Observe that you are not prompted when SSHing to instance, as cloud-init has not run again.

Success (upgrade from not broken->fixed):
1) Boot an Azure instance using an image with a pre-broken kernel (e.g. b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
2) Install the new version of cloud-init.
3) Upgrade to the fixed kernel (once it is available) and reboot.
4) Observe that you are not prompted when SSHing to instance, as cloud-init has not run again.

[Regression Potential]

The change is limited to the Azure data source. It affects how instance IDs are determined, but the change does so in a limited way.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1551419

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
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Raising to critical as this breaks Azure users.

Changed in linux (Ubuntu):
importance: Undecided → Critical
Ben Howard (darkmuggle) wrote :

Stephen, can you please tell us what the affected kernel versions are?

Brad Figg (brad-figg) wrote :

This commit is in the upstream kernel tree and has been backported to every Ubuntu kernel.

Ben Howard (darkmuggle) on 2016-02-29
affects: linux (Ubuntu) → cloud-init (Ubuntu)
Ben Howard (darkmuggle) wrote :

Azure has suggested that the test is simple:

$ [ $(sudo cat /sys/class/dmi/id/product_uuid) == $(sudo dmidecode -s system-uuid) ] || echo This system has the UUID bug

Dan Watkins (daniel-thewatkins) wrote :

OK, so I've done a bit of digging.

As of SMBIOS 2.6 (released in 2008), the first three fields of the UUID are well-defined as being encoded in little-endian. Before that, they could be encoded in "network byte order" (i.e. big-endian) if people felt like it.

Presumably enough people did feel like it, as dmidecode specifically has different code paths for pre-2.6 and post-2.6 SMBIOS versions; it will decode pre-2.6 UUIDs as big-endian and post-2.6 UUIDs as little-endian. (The comment in the dmidecode source code at [0] explains this pretty well.)

And, you've guessed it, Azure reports a pre-2.6 version of SMBIOS. (To be precise, 2.3, which was released in _1999_; Azure is old skool cool). This explains the difference between the kernel-reported UUID (always little-endian) and the dmidecode-reported UUID (big-endian on Azure, but little-endian on most modern systems).

[0] https://github.com/mirror/dmidecode/blob/master/dmidecode.c#L415

tags: added: kernel-da-key
Stephen A. Zarkos (stevez) wrote :

Hi Dan,

This issue does not repro with the latest Wily kernel, but it should, right? Can you help me understand why?

This is just testing on Hyper-V:

    # uname -r
    4.2.0-30-generic
    # cat /sys/class/dmi/id/product_uuid && dmidecode -s system-uuid
    EF6EED16-EAD5-BC4C-AD75-550370C212EE
    EF6EED16-EAD5-BC4C-AD75-550370C212EE

    # uname -r
    3.19.0-51-generic
    # cat /sys/class/dmi/id/product_uuid && dmidecode -s system-uuid
    16ED6EEF-D5EA-4CBC-AD75-550370C212EE
    EF6EED16-EAD5-BC4C-AD75-550370C212EE

Changed in cloud-init (Ubuntu):
assignee: nobody → Dan Watkins (daniel-thewatkins)
Dan Watkins (daniel-thewatkins) wrote :

OK, I'm shifting this back to linux, because I think that the commit that was backported is fixing a problem in a commit that _wasn't_ backported, therefore causing the issue. Here are the details:

In 95be58df7 [0], support for SMBIOS 3 was added, which introduces a third version field (i.e. 3.2.1 vs. 2.9); as a result, dmi_ver is converted from a u16 and a u32, and when it's read in, it's left-shifted 8 bits. (i.e. version 2.6 goes from 0x0206 to 0x020600). The endian-ness checks are updated to match the shifted number (i.e. if SMBIOS version >= 0x020600, little-endian, otherwise big-endian). This patch has NOT been backported to trusty.

In ff4319dc7 [1], it was identified that this left-shifting happened in the wrong place, and so it was moved to happen in a different place. Simple enough. However, this patch HAS been backported to trusty, despite the fact it is fixing behaviour that wasn't backported.

Crucially, though, the commit containing the backport [2] introduced the left-shifting _without_ changing the endian-ness checks. This means that the trusty kernel _always_ detects the SMBIOS version as being greater than 2.6, which means on older versions of SMBIOS (like the one in use on Azure), it returns the version with incorrect endian-ness.

[0] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/dmi_scan.c?id=95be58df74a5b21e5a78e45fddb2fd59112524c5
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/dmi_scan.c?id=ff4319dc7cd58c92b389960e375038335d157a60
[2] http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

affects: cloud-init (Ubuntu) → linux (Ubuntu)
Dan Watkins (daniel-thewatkins) wrote :

Thanks to Steve Z for pointing out that it works in wily; that's what sent me down this path.

It works in wily because wily _does_ have 95be58df7.

So in addition to a kernel fix, we will first need to release a cloud-init that will handle the endian-ness of instance IDs changing underneath it.

This is because the kernel is already out in the wild, so we will have some instances that have booted with the new UUID and the kernel fix will also trigger the behaviour seen in this bug.

Changed in cloud-init (Ubuntu):
assignee: nobody → Dan Watkins (daniel-thewatkins)
Changed in cloud-init (Ubuntu):
status: New → In Progress
Changed in linux (Ubuntu):
assignee: Dan Watkins (daniel-thewatkins) → nobody
Luis Henriques (henrix) on 2016-03-02
Changed in linux (Ubuntu Trusty):
status: New → Fix Committed
Luis Henriques (henrix) on 2016-03-02
Changed in linux (Ubuntu Vivid):
status: New → Fix Committed
description: updated
description: updated
Stephen A. Zarkos (stevez) wrote :

It seems the Utopic kernel is impacted as well, I tested 3.16.0-62-generic released on 2/27. I thought that kernel was EOL. Can we revert the fix here as well?

Andy Whitcroft (apw) on 2016-03-03
Changed in linux (Ubuntu Trusty):
importance: Undecided → Critical
Changed in linux (Ubuntu Vivid):
importance: Undecided → Critical
Changed in linux (Ubuntu Trusty):
assignee: nobody → Luis Henriques (henrix)
Changed in linux (Ubuntu Vivid):
assignee: nobody → Luis Henriques (henrix)
Luis Henriques (henrix) on 2016-03-03
Changed in linux-lts-utopic (Ubuntu Vivid):
status: New → Invalid
Changed in linux-lts-utopic (Ubuntu Trusty):
status: New → Fix Committed
assignee: nobody → Luis Henriques (henrix)
Andy Whitcroft (apw) on 2016-03-03
Changed in linux-lts-utopic (Ubuntu Trusty):
importance: Undecided → Critical
Andy Whitcroft (apw) on 2016-03-03
Changed in linux-keystone (Ubuntu Vivid):
status: New → Invalid
Changed in linux-keystone (Ubuntu):
status: New → Invalid
Changed in linux-keystone (Ubuntu Trusty):
status: New → Fix Committed
assignee: nobody → Luis Henriques (henrix)
importance: Undecided → Critical
description: updated

Attached is a debdiff for trusty (the only affected version).

Changed in cloud-init (Ubuntu Trusty):
status: New → In Progress
assignee: nobody → Dan Watkins (daniel-thewatkins)
Changed in cloud-init (Ubuntu):
status: In Progress → Invalid
assignee: Dan Watkins (daniel-thewatkins) → nobody
Changed in cloud-init (Ubuntu Vivid):
status: New → Invalid
summary: - Fix UUID endianness patch breaks cloud-init on Azure
+ [SRU] Fix UUID endianness patch breaks cloud-init on Azure
summary: - [SRU] Fix UUID endianness patch breaks cloud-init on Azure
+ [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Hello Stephen, or anyone else affected,

Accepted cloud-init into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.5-0ubuntu1.17 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in cloud-init (Ubuntu Trusty):
status: In Progress → Fix Committed
tags: added: verification-needed

I have tested all of the above cases with the cloud-init from -proposed and it behaved as expected.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.17

---------------
cloud-init (0.7.5-0ubuntu1.17) trusty; urgency=medium

  * Microsoft Azure:
    - d/patches/lp-1551419-azure-handle-flipped-uuid-endianness.patch: Handle
      cases where the endianness of the DMI UUID used for the instance ID has
      changed since last boot.(LP: #1551419)

 -- Daniel Watkins <email address hidden> Wed, 02 Mar 2016 14:23:18 +0000

Changed in cloud-init (Ubuntu Trusty):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

tags: added: patch
Brad Figg (brad-figg) on 2016-03-09
Changed in linux (Ubuntu):
status: Confirmed → Invalid
no longer affects: linux-lts-utopic (Ubuntu)
no longer affects: linux-lts-utopic (Ubuntu Vivid)
Launchpad Janitor (janitor) wrote :
Download full text (21.3 KiB)

This bug was fixed in the package linux - 3.19.0-56.62

---------------
linux (3.19.0-56.62) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1555832

  [ Florian Westphal ]

  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
    userspace
    - LP: #1555338

linux (3.19.0-55.61) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1554708

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon: call hpd_irq_event on resume"
    - LP: #1554608

linux (3.19.0-54.60) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1552337

  [ Upstream Kernel Changes ]

  * Revert "firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6"
    - LP: #1551419

linux (3.19.0-53.59) vivid; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
    - LP: #1550576

  [ Kamal Mostafa ]

  * Merged back 3.19.0-52.58

linux (3.19.0-52.58) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1548548

  [ Dan Streetman ]

  * SAUCE: nbd: ratelimit error msgs after socket close
    - LP: #1505564

  [ Upstream Kernel Changes ]

  * Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()"
    - LP: #1542457
  * Revert "workqueue: make sure delayed work run in local cpu"
    - LP: #1546320
  * net: ipmr: fix static mfc/dev leaks on table destruction
    - LP: #1542457
  * drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c
    - LP: #1542457
  * ovl: allow zero size xattr
    - LP: #1542457
  * ovl: use a minimal buffer in ovl_copy_xattr
    - LP: #1542457
  * [media] vb2: fix a regression in poll() behavior for output,streams
    - LP: #1542457
  * [media] gspca: ov534/topro: prevent a division by 0
    - LP: #1542457
  * [media] media: dvb-core: Don't force CAN_INVERSION_AUTO in oneshot mode
    - LP: #1542457
  * tools lib traceevent: Fix output of %llu for 64 bit values read on 32
    bit machines
    - LP: #1542457
  * KVM: x86: expose MSR_TSC_AUX to userspace
    - LP: #1542457
  * KVM: x86: correctly print #AC in traces
    - LP: #1542457
  * drm/radeon: call hpd_irq_event on resume
    - LP: #1542457
  * xhci: refuse loading if nousb is used
    - LP: #1542457
  * arm64: Clear out any singlestep state on a ptrace detach operation
    - LP: #1542457
  * time: Avoid signed overflow in timekeeping_get_ns()
    - LP: #1542457
  * ovl: root: copy attr
    - LP: #1542457
  * Bluetooth: Add support of Toshiba Broadcom based devices
    - LP: #1522949, #1542457
  * rtlwifi: fix memory leak for USB device
    - LP: #1542457
  * wlcore/wl12xx: spi: fix oops on firmware load
    - LP: #1542457
  * ovl: check dentry positiveness in ovl_cleanup_whiteouts()
    - LP: #1542457
  * EDAC, mc_sysfs: Fix freeing bus' name
    - LP: #1542457
  * EDAC: Robustify workqueues destruction
    - LP: #1542457
  * arm64: mm: ensure that the zero page is visible to the page table
    walker
    - LP: #1542457
  * powerpc: Make value-returning atomics fully ordered
    - LP: #1542457
  * powerpc: Make {cmp}xchg* and their atomic_ versions fully ordered
    - LP: #1542457
  * dm space map metadata: remove unused variable in brb_pop()
    - LP: #1542457
  * dm thi...

Changed in linux (Ubuntu Vivid):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (14.5 KiB)

This bug was fixed in the package linux - 3.13.0-83.127

---------------
linux (3.13.0-83.127) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1555839

  [ Florian Westphal ]

  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
    userspace
    - LP: #1555338

linux (3.13.0-82.126) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1554732

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon: call hpd_irq_event on resume"
    - LP: #1554608
  * net: generic dev_disable_lro() stacked device handling
    - LP: #1547680

linux (3.13.0-81.125) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1552316

  [ Upstream Kernel Changes ]

  * Revert "firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6"
    - LP: #1551419
  * bcache: Fix a lockdep splat in an error path
    - LP: #1551327

linux (3.13.0-80.124) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1548519

  [ Andy Whitcroft ]

  * [Debian] hv: hv_set_ifconfig -- convert to python3
    - LP: #1506521
  * [Debian] hv: hv_set_ifconfig -- switch to approved indentation
    - LP: #1540586
  * [Debian] hv: hv_set_ifconfig -- fix numerous parameter handling issues
    - LP: #1540586

  [ Dan Streetman ]

  * SAUCE: nbd: ratelimit error msgs after socket close
    - LP: #1505564

  [ Upstream Kernel Changes ]

  * Revert "workqueue: make sure delayed work run in local cpu"
    - LP: #1546320
  * [media] gspca: ov534/topro: prevent a division by 0
    - LP: #1542497
  * [media] media: dvb-core: Don't force CAN_INVERSION_AUTO in oneshot mode
    - LP: #1542497
  * tools lib traceevent: Fix output of %llu for 64 bit values read on 32
    bit machines
    - LP: #1542497
  * KVM: x86: correctly print #AC in traces
    - LP: #1542497
  * drm/radeon: call hpd_irq_event on resume
    - LP: #1542497
  * xhci: refuse loading if nousb is used
    - LP: #1542497
  * arm64: Clear out any singlestep state on a ptrace detach operation
    - LP: #1542497
  * time: Avoid signed overflow in timekeeping_get_ns()
    - LP: #1542497
  * rtlwifi: fix memory leak for USB device
    - LP: #1542497
  * wlcore/wl12xx: spi: fix oops on firmware load
    - LP: #1542497
  * EDAC, mc_sysfs: Fix freeing bus' name
    - LP: #1542497
  * EDAC: Don't try to cancel workqueue when it's never setup
    - LP: #1542497
  * EDAC: Robustify workqueues destruction
    - LP: #1542497
  * powerpc: Make value-returning atomics fully ordered
    - LP: #1542497
  * powerpc: Make {cmp}xchg* and their atomic_ versions fully ordered
    - LP: #1542497
  * dm space map metadata: remove unused variable in brb_pop()
    - LP: #1542497
  * dm thin: fix race condition when destroying thin pool workqueue
    - LP: #1542497
  * futex: Drop refcount if requeue_pi() acquired the rtmutex
    - LP: #1542497
  * drm/radeon: clean up fujitsu quirks
    - LP: #1542497
  * mmc: sdio: Fix invalid vdd in voltage switch power cycle
    - LP: #1542497
  * mmc: sdhci: Fix sdhci_runtime_pm_bus_on/off()
    - LP: #1542497
  * udf: limit the maximum number of indirect extents in a row
    - LP: #1542497
  * nfs: Fix race in __update_open_stateid...

Changed in linux (Ubuntu Trusty):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (15.5 KiB)

This bug was fixed in the package linux-lts-utopic - 3.16.0-67.87~14.04.1

---------------
linux-lts-utopic (3.16.0-67.87~14.04.1) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1555847

  [ Florian Westphal ]

  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
    userspace
    - LP: #1555338

linux-lts-utopic (3.16.0-66.86~14.04.1) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1555277

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon: call hpd_irq_event on resume"
    - LP: #1554608

linux-lts-utopic (3.16.0-65.85~14.04.1) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1552352

  [ Upstream Kernel Changes ]

  * Revert "firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6"
    - LP: #1551419

linux-lts-utopic (3.16.0-64.84~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
    - LP: #1550605

  [ Kamal Mostafa ]

  * Merged back 3.16.0-63.83~14.04.1

linux-lts-utopic (3.16.0-63.83~14.04.1) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1548934

  [ Dan Streetman ]

  * SAUCE: nbd: ratelimit error msgs after socket close
    - LP: #1505564

  [ Upstream Kernel Changes ]

  * Revert "workqueue: make sure delayed work run in local cpu"
    - LP: #1546320
  * drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c
    - LP: #1543126
  * veth: don’t modify ip_summed; doing so treats packets with bad
    checksums as good.
    - LP: #1543126
  * sctp: sctp should release assoc when sctp_make_abort_user return NULL
    in sctp_close
    - LP: #1543126
  * connector: bump skb->users before callback invocation
    - LP: #1543126
  * unix: properly account for FDs passed over unix sockets
    - LP: #1543126
  * bridge: Only call /sbin/bridge-stp for the initial network namespace
    - LP: #1543126
  * vxlan: fix test which detect duplicate vxlan iface
    - LP: #1543126
  * net: sctp: prevent writes to cookie_hmac_alg from accessing invalid
    memory
    - LP: #1543126
  * tcp_yeah: don't set ssthresh below 2
    - LP: #1543126
  * bonding: Prevent IPv6 link local address on enslaved devices
    - LP: #1543126
  * phonet: properly unshare skbs in phonet_rcv()
    - LP: #1543126
  * net: bpf: reject invalid shifts
    - LP: #1543126
  * ipv6: update skb->csum when CE mark is propagated
    - LP: #1543126
  * team: Replace rcu_read_lock with a mutex in team_vlan_rx_kill_vid
    - LP: #1543126
  * xen-netback: respect user provided max_queues
    - LP: #1543126
  * xen-netfront: respect user provided max_queues
    - LP: #1543126
  * xen-netfront: print correct number of queues
    - LP: #1543126
  * xen-netfront: update num_queues to real created
    - LP: #1543126
  * sctp: Prevent soft lockup when sctp_accept() is called during a timeout
    event
    - LP: #1543126
  * sctp: convert sack_needed and sack_generation to bits
    - LP: #1543126
  * sctp: start t5 timer only when peer rwnd is 0 and local state is
    SHUTDOWN_PENDING
    - LP: #1543126
  * nfs: Fix unused variable error
    - LP: #1543126
  * [media] gspca: ov534/topro: prevent a division by 0
    - LP: #1543126
  * [me...

Changed in linux-lts-utopic (Ubuntu Trusty):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-keystone - 3.13.0-53.78

---------------
linux-keystone (3.13.0-53.78) trusty; urgency=low

  [ Ike Panhc ]

  * Release Tracking Bug
    - LP: #1555956
  * Rebase to Ubuntu-3.13.0-83.127

  [ Ubuntu: 3.13.0-83.127 ]

  * Release Tracking Bug
    - LP: #1555839
  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
    userspace
    - LP: #1555338

 -- Ike Panhc <email address hidden> Sat, 12 Mar 2016 10:03:08 +0800

Changed in linux-keystone (Ubuntu Trusty):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers