From: Nicolas Schier <nsc@kernel.org>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
linux-kbuild@vger.kernel.org,
Uday Shankar <ushankar@purestorage.com>
Subject: Re: Since 6.18.x make binrpm-pkg does not sign modules
Date: Thu, 15 Jan 2026 09:30:32 +0100 [thread overview]
Message-ID: <aWilqPP-udHWtiu1@derry.ads.avm.de> (raw)
In-Reply-To: <71934f81-c412-cdaa-421b-b3b599be756d@praktifix.dwd.de>
On Sun, Jan 11, 2026 at 06:41:39PM +0100, Holger Kiehl wrote:
> On Sat, 10 Jan 2026, Nicolas Schier wrote:
>
> > A simple solution might be to call modules_sign target after the
> > find-debuginfo.sh run; but commit 16c36f8864e3 spunds to me as if we
> > should rather do something similiar as for the Debian packages:
> > modules_install with INSTALL_MOD_STRIP=1 and then install only the debug
> > infos manually.
> >
> > Does that make sense?
> >
> I am not a kernel developer and my knowledge in this area is very
> limited. Did try your suggestion to call modules_install with
> INSTALL_MOD_STRIP=1, but still the signature was removed in the
> RPM. Removing the 'chmod u+x', so find-debuginfo.sh does not strip
> them, did not help either. But, most properly, I am still missing
> something.
I am going to have a closer look at that, but that will take time.
A possible work-around might be to enable CONFIG_MODULE_COMPRESS and
CONFIG_MODULE_COMPRESS_ALL, which prevents find-debuginfo.sh from
stripping (but you won't get debug modules, too).
Kind regards,
Nicolas
next prev parent reply other threads:[~2026-01-15 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 14:04 Since 6.18.x make binrpm-pkg does not sign modules Holger Kiehl
2026-01-09 21:06 ` Nicolas Schier
2026-01-10 11:43 ` Holger Kiehl
2026-01-10 21:34 ` Nicolas Schier
2026-01-11 17:41 ` Holger Kiehl
2026-01-15 8:30 ` Nicolas Schier [this message]
2026-01-20 0:04 ` Nathan Chancellor
2026-01-20 23:21 ` Holger Kiehl
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=aWilqPP-udHWtiu1@derry.ads.avm.de \
--to=nsc@kernel.org \
--cc=Holger.Kiehl@dwd.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ushankar@purestorage.com \
/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