[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: Fix Released Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Merge proposal unlinked: https://code.launchpad.net/~dannf/+git/maas-preseeds/+merge/411293 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Merge proposal linked: https://code.launchpad.net/~dannf/+git/maas-preseeds/+merge/411293 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
This bug was fixed in the package linux-base - 4.5ubuntu5.4 --- linux-base (4.5ubuntu5.4) hirsute; urgency=medium * linux-version: Fix sorting of versions provided via stdin to match the output when provided via argv (LP: #1926985). -- dann frazier Wed, 07 Jul 2021 14:13:01 -0600 ** Changed in: linux-base (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
This bug was fixed in the package linux-base - 4.5ubuntu1.7 --- linux-base (4.5ubuntu1.7) bionic; urgency=medium * linux-version: Fix sorting of versions provided via stdin to match the output when provided via argv (LP: #1926985). -- dann frazier Wed, 07 Jul 2021 14:34:55 -0600 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
This bug was fixed in the package linux-base - 4.5ubuntu3.7 --- linux-base (4.5ubuntu3.7) focal; urgency=medium * linux-version: Fix sorting of versions provided via stdin to match the output when provided via argv (LP: #1926985). -- dann frazier Wed, 07 Jul 2021 14:20:10 -0600 ** Changed in: linux-base (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-base (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Tags added: verification-done verification-done-bionic verification- done-focal verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
The above test failures all seemed to pass upon re-run. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
= Verification =
$ cat versions.txt
5.8.0-50-generic
5.8.0-50-generic-64k
$ for dist in hirsute groovy focal bionic; do
lxc exec dannf-lp1926985-${dist} -- dpkg-query --showformat='${Version}\n'
--show linux-base; lxc exec dannf-lp1926985-${dist} -- linux-version sort <
versions.txt; done
4.5ubuntu5.4
5.8.0-50-generic
5.8.0-50-generic-64k
4.5ubuntu4.1
5.8.0-50-generic
5.8.0-50-generic-64k
4.5ubuntu3.7
5.8.0-50-generic
5.8.0-50-generic-64k
4.5ubuntu1.7
5.8.0-50-generic
5.8.0-50-generic-64k
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1926985
Title:
linux-version sort: argv and stdin behaviors differ
Status in linux-base package in Ubuntu:
Fix Released
Status in linux-base source package in Bionic:
Fix Committed
Status in linux-base source package in Focal:
Fix Committed
Status in linux-base source package in Groovy:
Fix Committed
Status in linux-base source package in Hirsute:
Fix Committed
Status in linux-base source package in Impish:
Fix Released
Status in linux-base package in Debian:
New
Bug description:
[Impact]
`linux-version sort` provides 2 ways to sort kernel version strings: users
can provide these strings either via the command line or via stdin. Currently
these methods give different answers for certain version strings (see Test
Case). The stdin behavior is decidedly incorrect, and this is the mode
flash-kernel uses. As a real world example, a user with an arm64 u-boot system
might end up booting 5.8.0-50-generic instead of the expected
5.8.0-50-generic-64k if both are installed. There maybe additional issues
caused by this; for example, I found this with our automation that tests
kernels on various arm64 platforms in version increasing order. Only after
consulting logs did we realize that 64k kernels were not ever getting booted
because the tooling (which uses argv mode) disagreed with the kernel installer
(flash-kernel using stdin mode) about which kernel should be the default.
It's possible this internal discrepancy can cause other issues due to
tools disagreeing about which kernel is the latest, but the flash-
kernel example is the only one I'm aware of at this point.
[Test Case]
Using argv:
$ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k
5.8.0-50-generic
5.8.0-50-generic-64k
Using stdin (incorrect):
$ cat versions.txt
5.8.0-50-generic
5.8.0-50-generic-64k
$ cat versions.txt | linux-version sort
5.8.0-50-generic-64k
5.8.0-50-generic
[Where Problems Could Occur]
An obvious place where problems could occur is if someone is relying on
rebooting into the kernel that is incorrectly being sorted greatest. For those
using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic
vs. generic-64k case used in the examples above. The generic-64k flavor is
available in >= 20.10, as well as 20.04-hwe. ARM server users - those most
likely to want the generic-64k flavor - are very unlikely to be using
flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and
are unaffected by this change. We found this on an HP m400 platform which is
the only Ubuntu certified u-boot-based arm64 server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
Hello dann, or anyone else affected, Accepted linux-base into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu5.4 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 on 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, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-base (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux-base (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Description changed: [Impact] - Systems that use flash-kernel may end up installing the wrong kernel image. - - `linux-version sort` can provide different answers depending on how it - is called (see Test Case). The stdin behavior appears to be a bug, and - this is the mode flash-kernel uses. So, for example, a user with an - arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of - the expected 5.8.0-50-generic if both are installed. There maybe - additional issues caused by this; for example, I found this with our - automation that tests kernels on various arm64 platforms in version - increasing order. Only after consulting logs did we realize that 64k - kernels were not ever getting booted because the tooling (which uses - argv mode) disagreed with the kernel installer (flash-kernel using stdin - mode) about which kernel should be the default. + `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash-kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: In Progress Status in linux-base source package in Focal: In Progress Status in linux-base source package in Groovy: In Progress Status in linux-base source package in Hirsute: In Progress Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Description changed: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. + + It's possible this internal discrepancy can cause other issues due to + tools disagreeing about which kernel is the latest, but the flash-kernel + example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] - An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. + An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: In Progress Status in linux-base source package in Focal: In Progress Status in linux-base source package in Groovy: In Progress Status in linux-base source package in Hirsute: In Progress Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-base (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux-base (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-base (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: In Progress Status in linux-base source package in Focal: In Progress Status in linux-base source package in Groovy: In Progress Status in linux-base source package in Hirsute: In Progress Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Ubuntu Hirsute) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-base (Ubuntu Focal) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-base (Ubuntu Groovy) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-base (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: New Status in linux-base source package in Focal: New Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: New Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Also affects: linux-base (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-base (Ubuntu Impish) Importance: Undecided Assignee: dann frazier (dannf) Status: Fix Released ** Also affects: linux-base (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-base (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-base (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: New Status in linux-base source package in Focal: New Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: New Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
This bug was fixed in the package linux-base - 4.5ubuntu6 --- linux-base (4.5ubuntu6) impish; urgency=medium * linux-version: Fix sorting of versions provided via stdin to match the output when provided via argv (LP: #1926985). -- dann frazier Mon, 03 May 2021 10:16:43 -0600 ** Changed in: linux-base (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Ubuntu) Status: New => In Progress ** Changed in: linux-base (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: In Progress Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: New Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
