From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
linux-modules@vger.kernel.org
Subject: Re: Unbootable system with kmod-31
Date: Tue, 3 Oct 2023 21:02:32 -0400 [thread overview]
Message-ID: <df84e672-81f2-4f48-a5cf-65eb05ecc242@moonlit-rail.com> (raw)
In-Reply-To: <mmsrsxnmplo7zvh2rmp3zvymaprxj73mrskdjwngfnawkoh5ur@xx5dclgmv6bg>
Lucas De Marchi wrote:
> On Tue, Oct 03, 2023 at 11:08:29PM +0200, Marco d'Itri wrote:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050586
>
> duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050582 ?
Ah, that does seem the better bug report, as it triages it down to the
dictionary size.
> Maybe that patch needs to propagate back to 6.5?
If you mean that modules_install doesn't pass the right parameters to
/bin/xz, then definitely. I've reported on bugzilla variously over the
years about things "fixed in Linus's tree" that never got queued into
Greg KH's tree.
Perhaps kmod should be updated to only call finit_module() when the
kernel_version is >= known good, or when not using xz compression, and
use init_module() elsewhere?
In any case, I didn't see the Debian bug report earlier. Using
Slackware here with custom-config mainline kernels.
Kris
next prev parent reply other threads:[~2023-10-04 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 20:55 Unbootable system with kmod-31 Kris Karas (Bug Reporting)
2023-10-03 21:08 ` Marco d'Itri
2023-10-03 23:37 ` Lucas De Marchi
2023-10-04 1:02 ` Kris Karas (Bug Reporting) [this message]
2023-10-04 2:44 ` Lucas De Marchi
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=df84e672-81f2-4f48-a5cf-65eb05ecc242@moonlit-rail.com \
--to=bugs-a21@moonlit-rail.com \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.demarchi@intel.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