From: Andrea Righi <andrea.righi@canonical.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Lucas De Marchi <lucas.de.marchi@gmail.com>,
linux-modules@vger.kernel.org
Subject: Re: [PATCH] libkmod: allow to fallback to user-space decompression
Date: Tue, 29 Aug 2023 19:10:11 +0200 [thread overview]
Message-ID: <ZO4mc0aJHJj5IiuC@righiandr-XPS-13-7390> (raw)
In-Reply-To: <ZO4gA5mhGK1nN54Q@bombadil.infradead.org>
On Tue, Aug 29, 2023 at 09:42:43AM -0700, Luis Chamberlain wrote:
> On Tue, Aug 29, 2023 at 05:23:25PM +0200, Andrea Righi wrote:
> > For the records, I've also sent this patch to address the issue from a
> > kernel perspective:
> > https://lore.kernel.org/lkml/20230829120508.317611-1-andrea.righi@canonical.com/T/#u
> >
> > That seems to solve the issue in my particular case, but I'm not sure if
> > that's a valid solution across all architectures.
>
> I can't think of a reason why it would regress on other architectures.
> We'll give it a spin soon fast as it will be on its way to Linus today.
Cool! Yes, if this patch can be applied we don't really need to change
libkmod and if there are other spots in the decompress code that can use
vmalloc() we can adjust them in a similar way.
Thanks,
-Andrea
next prev parent reply other threads:[~2023-08-29 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 12:38 [PATCH] libkmod: allow to fallback to user-space decompression Andrea Righi
2023-08-29 14:47 ` Lucas De Marchi
2023-08-29 15:23 ` Andrea Righi
2023-08-29 16:42 ` Luis Chamberlain
2023-08-29 17:10 ` Andrea Righi [this message]
2023-08-29 16:49 ` 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=ZO4mc0aJHJj5IiuC@righiandr-XPS-13-7390 \
--to=andrea.righi@canonical.com \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@intel.com \
--cc=mcgrof@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).