https://rancher.com/ logo
Join Slack
Powered by
Does anyone happen to have the host kernel version...
# harvester
b
Does anyone happen to have the host kernel version that's shipped with 1.6.0?
t
Looks like 5.14.21
b
That's a bummer.
t
I think that is wrong.. I think it is 6.10.. let me check 1 more box.
damm same
second one I upgrade. 1st, I rebuilt.
rebuilding a node from iso now to triple check.
b
5.14.21-150500.55.103-default
?
t
maybe
b
iirc the version from 1.4.3 to 1.5.1 didn't change, but I was under the impression that 1.6.0 was going to have some additional patches.
t
I thought it was supposed to be 6.1….
b
I was hoping at least for a minor bump to like 5.17 or something.
t
confirmed 
5.14.21
b
Do you have the patch versions too?
t
command?
b
uname -r
t
Copy code
rancher@slim:~> uname -r
5.14.21-150500.55.116-default
b
Ok, so it's not the same the same
Suse adds a bunch of backports, we just don't publicly know what all is in the 103-116 changes.
Well I think technically they have to post the sourcecode somewhere, but it'd be a pain to figure it out
t
slight…
a
I really should write this up somewhere less ephemeral, but here's some tricks: Check kernel changelog for v1.5.1:
Copy code
> docker run --rm -it rancher/harvester-os:v1.5-20250625 rpm -q --changelog kernel-default|head
warning: Found NDB Packages.db database while attempting bdb backend: using ndb backend.
* Fri May 09 2025 <mailto:fmancera@suse.de|fmancera@suse.de>
- netfilter: conntrack: revisit the gc initial rescheduling bias
  (CVE-2022-49110 bsc#1237981).
- commit 7e1d902

* Fri May 09 2025 <mailto:fmancera@suse.de|fmancera@suse.de>
- netfilter: conntrack: fix the gc rescheduling delay
  (CVE-2022-49110 bsc#1237981).
- commit 9cc8bdd
Check kernel changelog for v1.6.0:
Copy code
> docker run --rm -it rancher/harvester-os:v1.6-20250826 rpm -q --changelog kernel-default|head
warning: Found NDB Packages.db database while attempting bdb backend: using ndb backend.
* Wed Jul 23 2025 <mailto:fmancera@suse.de|fmancera@suse.de>
- netfilter: nf_tables: mark set as dead when unbinding anonymous
  set with timeout (CVE-2024-26643 bsc#1221829).
- commit 4daa764

* Tue Jul 22 2025 <mailto:fmancera@suse.de|fmancera@suse.de>
- netfilter: allow exp not to be removed in nf_ct_find_expectation
  (CVE-2023-52927 bsc#1239644).
- commit b3f811c
So there's a bunch of stuff added since v1.5.1 Get more info about kernel-default in v1.6:
Copy code
> docker run --rm -it rancher/harvester-os:v1.6-20250826 rpm -qi kernel-default
warning: Found NDB Packages.db database while attempting bdb backend: using ndb backend.
Name        : kernel-default
Version     : 5.14.21
Release     : 150500.55.116.1
Architecture: x86_64
Install Date: Mon Aug 25 09:34:53 2025
Group       : System/Kernel
Size        : 191185307
License     : GPL-2.0-only
Signature   : RSA/SHA256, Fri Jul 25 16:18:52 2025, Key ID 70af9e8139db7c82
Source RPM  : kernel-default-5.14.21-150500.55.116.1.nosrc.rpm
Build Date  : Fri Jul 25 16:12:08 2025
Build Host  : h01-ch4a
Relocations : (not relocatable)
Packager    : <https://www.suse.com/>
Vendor      : SUSE LLC <<https://www.suse.com/>>
URL         : <https://www.kernel.org/>
Summary     : The Standard Kernel
Description :
The standard kernel for both uniprocessor and multiprocessor systems.


Source Timestamp: 2025-07-24 18:28:14 +0000
GIT Revision: 0e3b4d7a1837cd115dc4b4b04a99f5f947f2892b
GIT Branch: SLE15-SP5-LTSS
Distribution: SUSE Linux Enterprise 15
Note that git revision. That maps to: https://github.com/SUSE/kernel-source/commit/0e3b4d7a1837cd115dc4b4b04a99f5f947f2892b https://github.com/SUSE/kernel-source is our patches that are applied on top of the upstream kernel source, and I assume that's a pain to browse if you're not a kernel engineer, which I'm not 😉 https://github.com/SUSE/kernel is the upstream sources with our patches applied, which is easy(ier) to browse. The branch you want is https://github.com/SUSE/kernel/tree/SLE15-SP5-RT-LTSS. The one thing I haven't figured out is exactly how to easily determine which commit on that branch matches a particular kernel version. That branch has a bunch more commits since July 25, when the kernel we're talking about was built. You can figure it out by looking at the commit history, but I'm kinda hoping there's a better way. Anyway, hope that helps 🙂
🚀 1
p
yikes
Open in Slack
PreviousNext
Powered by