linux-kernel - Re: [PROBLEM linux-next] Segfault while building headers with dpkg-deb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAK7LNAQsMAw_+wwtmC1JoG+wkJscZyJ3oqqFYbuCL9ynVordRQ@mail.gmail.com>
Date: Sat, 6 Jul 2024 14:24:53 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Mirsad Todorovac <mtodorovac69@...il.com>
Cc: Linux Kernel Build System <linux-kbuild@...r.kernel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PROBLEM linux-next] Segfault while building headers with dpkg-deb

On Sat, Jul 6, 2024 at 5:57 AM Mirsad Todorovac <mtodorovac69@...il.com> wrote:
>
> On 7/2/24 10:18, Masahiro Yamada wrote:
> > On Sat, Jun 29, 2024 at 3:59 AM Mirsad Todorovac <mtodorovac69@...il.com> wrote:
> >>
> >> Hi all,
> >>
> >> On the vanilla linux-next tree, branch next-20240627, there happens to be a bug while building
> >> with the randconfig seed KCONFIG_SEED=0x90E8E591:
> >>
> >>   .
> >>   .
> >>   .
> >>   XZ      debian/linux-image-6.10.0-rc5-next-20240627-dirty/lib/modules/6.10.0-rc5-next-20240627-dirty/kernel/samples/trace_events/trace-events-sample.ko.xz
> >>   XZ      debian/linux-image-6.10.0-rc5-next-20240627-dirty/lib/modules/6.10.0-rc5-next-20240627-dirty/kernel/samples/trace_events/trace_custom_sched.ko.xz
> >>   XZ      debian/linux-image-6.10.0-rc5-next-20240627-dirty/lib/modules/6.10.0-rc5-next-20240627-dirty/kernel/samples/ftrace/sample-trace-array.ko.xz
> >>   XZ      debian/linux-image-6.10.0-rc5-next-20240627-dirty/lib/modules/6.10.0-rc5-next-20240627-dirty/kernel/samples/fprobe/fprobe_example.ko.xz
> >> dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_6.10.0-rc5-45_i386.deb'.
> >>   DEPMOD  debian/linux-image-6.10.0-rc5-next-20240627-dirty/lib/modules/6.10.0-rc5-next-20240627-dirty
> >> dpkg-deb: building package 'linux-headers-6.10.0-rc5-next-20240627-dirty' in '../linux-headers-6.10.0-rc5-next-20240627-dirty_6.10.0-rc5-45_i386.deb'.
> >> Segmentation fault (core dumped)
> >> make[6]: *** [scripts/Makefile.modinst:128: depmod] Error 139
> >> make[5]: *** [Makefile:1842: modules_install] Error 2
> >> make[4]: *** [Makefile:2058: run-command] Error 2
> >> make[3]: *** [debian/rules:61: binary-image] Error 2
> >> make[3]: *** Waiting for unfinished jobs....
> >> dpkg-deb: building package 'linux-image-6.10.0-rc5-next-20240627-dirty-dbg' in '../linux-image-6.10.0-rc5-next-20240627-dirty-dbg_6.10.0-rc5-45_i386.deb'.
> >> dpkg-buildpackage: error: make -f debian/rules binary subprocess returned exit status 2
> >> make[2]: *** [scripts/Makefile.package:121: bindeb-pkg] Error 2
> >> make[1]: *** [/home/marvin/linux/kernel/linux-next/Makefile:1555: bindeb-pkg] Error 2
> >> make: *** [Makefile:240: __sub-make] Error 2
> >>
> >> Build log and .config are attached at your convenience.
> >
> >
> >
> >
> >
> > If you used an old kmod version, this is a known issue.
> >
> > https://lore.kernel.org/linux-kbuild/E1rNVlL-000qDm-Pg@rmk-PC.armlinux.org.uk/
> >
> > A quick solution is to upgrade your kmod version.
>
> I see. Sorry then for the noise and duplicated work.
>
> It might be inevitable that I will do something dumb more often than not when testing
> randconfig errors from such a vast number of lines of code ... :-/
>
> My kmod is as follows:
>
> ii  kmod           29-1ubuntu1  amd64        tools for managing Linux kernel modules
>
> I thought of upgrading to 24.04 LTS, but when upgrading kmod I've lost the capacity to boot
> the older kernels in bisect process?
>
> Probably, it would be for the best if I had several versions of Ubuntu in multiple boot
> options? However, I have not yet done that ...
>


You do not need to install distributions on your bare metal.


I need varous test environments,
such as Debian, Ubuntu, Fedora, OpenSUSE, Arch, ...


For compile testing, I use Docker.
When I need to replace the kernel, I use Vagrant.


If you want to compile-test deb-pkg with randconfig,
Docker is enough.




--
Best Regards
Masahiro Yamada