The 3.13 kernel for Precise ESM does not provide the expected version number

Bug #1838610 reported by Po-Hsu Lin
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Po-Hsu Lin
linux (Ubuntu)
Fix Released

Bug Description

The linux-generic-lts-trusty meta package on Precise will give you:
  linux-base linux-headers-3.13.0-172 linux-headers-3.13.0-172-generic
  linux-headers-generic-lts-trusty linux-image-3.13.0-172-generic
  linux-image-generic-lts-trusty linux-modules-3.13.0-172-generic

And the kernel version returned from uname -a shows:
  Linux precise-testing 3.13.0-172-generic #1-Ubuntu SMP Sat Jul 6 10:46:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

This is breaking the automation as we're expecting the kernel version:

Tags: ckct kt trusty
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 1838610

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
tags: added: trusty
Revision history for this message
Andy Whitcroft (apw) wrote :

It does appear for other series we include the ~12.04.1 bit in the uname -a output:

    Linux kowtow-b64 5.0.0-21-generic #22~18.04.1-Ubuntu SMP Thu Jul 4 17:25:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

But it is likely best to use /proc/version_signature in preference to this.

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

Andy suggest us to use "cat /proc/version_signature"

This command on this Precise node shows:
Ubuntu 3.13.0-172.223~12.04.1-generic 3.13.11-ckt39

This looks more reliable than the "uname -vr"

Testing a workaround on KT.

He also found the bug that cause this issue.

Po-Hsu Lin (cypressyew)
tags: added: ckct kt
Po-Hsu Lin (cypressyew)
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in ubuntu-kernel-tests:
assignee: nobody → Po-Hsu Lin (cypressyew)
status: New → Fix Released
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

As we're just deploying P-ESM with KT

I think this will be fixed in the kernel, but as fix applied to the tool, marking this as fix-released.

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

Not sure if this should be "Invalid" for kernel itself. Re-open it.

This is affecting the SRU test this cycle with bug 1849079

Changed in linux (Ubuntu):
status: Invalid → Confirmed
Stefan Bader (smb)
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
Changed in linux (Ubuntu Trusty):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.2.0-150.197

linux (3.2.0-150.197) precise; urgency=medium

  * precise/linux: 3.2.0-150.197 -proposed tracker (LP: #1919172)

  * CVE-2021-27365
    - scsi: iscsi: Verify lengths on passthrough PDUs
    - sysfs: Add sysfs_emit and sysfs_emit_at to format sysfs output
    - scsi: iscsi: Ensure sysfs attributes are limited to PAGE_SIZE

  * CVE-2021-27363 // CVE-2021-27364
    - scsi: iscsi: Restrict sessions and handles to admin capabilities

  * CVE-2021-27364
    - scsi: iscsi: respond to netlink with unicast when appropriate
    - Add file_ns_capable() helper function for open-time capability checking
    - net: Add variants of capable for use on on sockets
    - netlink: Make the sending netlink socket availabe in NETLINK_CB

 -- Thadeu Lima de Souza Cascardo <email address hidden> Mon, 05 Apr 2021 14:23:29 -0300

Changed in linux (Ubuntu Precise):
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