Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #82405 > unrolled thread
| Started by | Tom Overlund <tomov@dilacero.org> |
|---|---|
| First post | 2024-05-12 17:00 +0200 |
| Last post | 2024-05-14 23:50 +0200 |
| Articles | 3 — 1 participant |
Back to article view | Back to linux.debian.kernel
Bug#1070986: linux-source-6.7: Signing error building 6.7 custom kernel Tom Overlund <tomov@dilacero.org> - 2024-05-12 17:00 +0200
Bug#1070986: linux-source-6.7: Signing error building 6.7 custom kernel Tom Overlund <tomov@dilacero.org> - 2024-05-14 01:10 +0200
Bug#1070986: This is a bug in debian scripts not upstream Tom Overlund <tomov@dilacero.org> - 2024-05-14 23:50 +0200
| From | Tom Overlund <tomov@dilacero.org> |
|---|---|
| Date | 2024-05-12 17:00 +0200 |
| Subject | Bug#1070986: linux-source-6.7: Signing error building 6.7 custom kernel |
| Message-ID | <IDiQ9-cRaI-3@gated-at.bofh.it> |
Package: linux-source-6.7 Version: 6.7.12-1 Severity: normal X-Debbugs-Cc: tomov@dilacero.org Dear Maintainer, I'm following the directions at the Kernel Handbook, "4.2. Building a custom kernel from Debian kernel source". I apt-get installed: linux-source libncurses-dev pahole I configured with: $ make localmodconfig and took defaults to any prompts. I then ran: $ make menuconfig and turned on: Kernel hacking->Generic Kernel Debugging Instruments->KGDB: kernel debugger (KGDB=y) And finally, ran: $ make bindeb-pkg The kernel compiled, but then failed with: ... HDRINST usr/include/asm/types.h INSTALL debian/linux-libc-dev/usr/include SIGN debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko At main.c:298: - SSL error:FFFFFFFF80000002:system library::No such file or directory: ../crypto/bio/bss_file.c:67 - SSL error:10000080:BIO routines::no such file: ../crypto/bio/bss_file.c:75 sign-file: debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko make[6]: *** [scripts/Makefile.modinst:137: debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko] Error 1 make[5]: *** [Makefile:1844: modules_install] Error 2 make[4]: *** [Makefile:2059: run-command] Error 2 make[3]: *** [debian/rules:17: binary-arch] Error 2 ESC[1mdpkg-buildpackage: ESC[0mESC[1;31merrorESC[0m: make -f debian/rules binary subprocess returned exit status 2 make[2]: *** [scripts/Makefile.package:144: bindeb-pkg] Error 2 make[1]: *** [/home/virt/linux-source-6.7/Makefile:1560: bindeb-pkg] Error 2 make: *** [Makefile:246: __sub-make] Error 2 I did some digging, and it looks like it's trying to double-sign the .ko files. For example, earlier in the make output, it says: run-command KBUILD_RUN_COMMAND=+./scripts/package/builddeb SYMLINK debian/linux-image/lib/modules/6.7.12/build INSTALL debian/linux-image/lib/modules/6.7.12/modules.order INSTALL debian/linux-image/lib/modules/6.7.12/modules.builtin INSTALL debian/linux-image/lib/modules/6.7.12/modules.builtin.modinfo INSTALL debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko SIGN debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko XZ debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko.xz And ls shows the .xz file is there: $ ls debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel* debian/linux-image/lib/modules/6.7.12/kernel/arch/x86/crypto/aesni-intel.ko.xz So then when it tries to sign the .ko file again, it can't find it, because it's been compressed to .xz. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-source-6.7 depends on: ii binutils 2.42-4 ii xz-utils 5.6.1+really5.4.5-1 Versions of packages linux-source-6.7 recommends: ii bc 1.07.1-4 ii bison 2:3.8.2+dfsg-1+b1 ii build-essential 12.10 ii cpio 2.15+dfsg-1 ii flex 2.6.4-8.2+b2 ii kmod 32-1 ii libelf-dev 0.191-1+b1 ii libssl-dev 3.2.1-3 ii linux-config-6.7 6.7.12-1 ii rsync 3.3.0-1 Versions of packages linux-source-6.7 suggests: ii libncurses-dev [ncurses-dev] 6.4+20240414-1 ii pkgconf [pkg-config] 1.8.1-1+b2 pn qtbase5-dev <none> -- no debconf information
[toc] | [next] | [standalone]
| From | Tom Overlund <tomov@dilacero.org> |
|---|---|
| Date | 2024-05-14 01:10 +0200 |
| Message-ID | <IDMXT-dapk-3@gated-at.bofh.it> |
| In reply to | #82405 |
This works in the 6.8.9 upstream kernel. So I guess the good news is it wil be fixed in Debian eventually.
[toc] | [prev] | [next] | [standalone]
| From | Tom Overlund <tomov@dilacero.org> |
|---|---|
| Date | 2024-05-14 23:50 +0200 |
| Subject | Bug#1070986: This is a bug in debian scripts not upstream |
| Message-ID | <IE8c1-dnAR-1@gated-at.bofh.it> |
| In reply to | #82405 |
It's actually upstream. I ran the same: $ make bindeb-pkg on the upstream source as I did on the Debian source, and yes, it gave me .deb packages. Here's the repo for the upstream script that was part of the problem: https://github.com/torvalds/linux/commits/master/scripts/package/builddeb Note the recent changes. I may be wrong, and it's a Debian patch that is causing the problem, but from what I've seen of the code it's probably upstream. I suppose I could download an upstream version of 6.7, and verify it has the same problem, but since nobody on the Debian maintainer side seems to care, I won't bother.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web