From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kernel Build System <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM linux-next] Segfault while building headers with dpkg-deb
Date: Fri, 5 Jul 2024 22:57:11 +0200 [thread overview]
Message-ID: <70b32083-34fb-42a5-b9bd-6f4fd21f70fd@gmail.com> (raw)
In-Reply-To: <CAK7LNASH6mS3X_YhkVV9z5ZVXdew_nGpJxaakaE1moZckETM7A@mail.gmail.com>
On 7/2/24 10:18, Masahiro Yamada wrote:
> On Sat, Jun 29, 2024 at 3:59 AM Mirsad Todorovac <mtodorovac69@gmail.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 ...
Best regards,
Mirsad Todorovac
> --
> Best Regards
> Masahiro Yamada
next prev parent reply other threads:[~2024-07-05 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 18:58 [PROBLEM linux-next] Segfault while building headers with dpkg-deb Mirsad Todorovac
2024-07-02 8:18 ` Masahiro Yamada
2024-07-05 20:57 ` Mirsad Todorovac [this message]
2024-07-06 5:24 ` Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70b32083-34fb-42a5-b9bd-6f4fd21f70fd@gmail.com \
--to=mtodorovac69@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox