jool-dkms FTBS with the latest linux 6.8 hwe on jammy

Bug #2072313 reported by Andrea Righi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jool (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

/var/lib/dkms/jool-dkms/4.1.7/build/src/mod/common/nl/nl_common.c: In function ‘get_jool_hdr’:
/var/lib/dkms/jool-dkms/4.1.7/build/src/mod/common/nl/nl_common.c:17:20: error: ‘struct genl_info’ has no member named ‘userhdr’
   17 | return info->userhdr;
      | ^~
/var/lib/dkms/jool-dkms/4.1.7/build/src/mod/common/nl/nl_common.c:18:1: error: control reaches end of non-void function [-Werror=return-type]
   18 | }
      | ^

[Test case]

install both GA and HWE kernels, and

 $ sudo apt install jool-dkms

then check that the build for both kernels succeeds

[Fix]

Backport the changes from Noble to properly support the new 6.8 kernel ABI.

[Regression potential]

Jool is an is an IP/ICMP translator, with this applied we may experience networking regressions with kernels >= 6.8.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: jool-dkms 4.1.7-1ubuntu1
ProcVersionSignature: User Name 6.8.0-35.35.1~22.04.1-lowlatency 6.8.4
Uname: Linux 6.8.0-35-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/vdb)
Date: Fri Jul 5 08:49:14 2024
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: jool
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Andrea Righi (arighi) wrote :
Revision history for this message
Andrea Righi (arighi) wrote :

Test plan linux hwe 6.8:

jool_common.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/

jool.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/

jool_siit.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/

Test plan GA kernel 5.15:
jool_common.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/

jool.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/

jool_siit.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/

Revision history for this message
Andrea Righi (arighi) wrote :
tags: added: patch
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Andrea, or anyone else affected,

Accepted jool into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/jool/4.1.7-1ubuntu2 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

description: updated
Changed in jool (Ubuntu):
status: New → Invalid
Changed in jool (Ubuntu Jammy):
status: New → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Paolo Pisati (p-pisati) wrote (last edit ):

$ dkms status
jool-dkms/4.1.7, 5.15.0-116-generic, x86_64: installed
jool-dkms/4.1.7, 6.8.0-38-generic, x86_64: installed

GA:
$ lsmod | grep jool
jool 20480 0
jool_common 237568 1 jool

HWE:
$ lsmod | grep jool
jool 16384 0
jool_common 323584 1 jool

build, install and load fine on GA and HWE kernels.

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jool - 4.1.7-1ubuntu2

---------------
jool (4.1.7-1ubuntu2) jammy; urgency=medium

  * Support Linux 6.8 (LP: #2072313):
    - debian/patches/0002-linux-6.8.patch

 -- Andrea Righi <email address hidden> Fri, 05 Jul 2024 08:55:38 +0000

Changed in jool (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for jool has completed successfully and the package is now being 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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