From: Rusty Russell <rusty@rustcorp.com.au>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: Andreas Mohr <andi@lisas.de>,
Andrew Morton <akpm@linux-foundation.org>,
Bertrand Jacquin <beber@meleeweb.net>, Marco d'Itri <md@linux.it>,
linux-modules <linux-modules@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>, Jon Masters <jcm@redhat.com>
Subject: Re: [PATCH] modules: CONFIG_MODULE_COMPRESS: add hint that userspace support may easily be missing.
Date: Fri, 05 Jun 2015 05:52:24 +0930 [thread overview]
Message-ID: <87zj4fte9r.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAKi4VA+4mFsg7VCqr+3wd4dCqUtCW02YP7KYmVYF0prH5bet0g@mail.gmail.com>
Lucas De Marchi <lucas.de.marchi@gmail.com> writes:
>> + gzip and xz (but doesn't by default, at least as of version 18!).
>
> This is pretty much misleading. There's no such a default option. It's
> like saying kernel doesn't support feature X, Y or Z by default
> because make defconfig doesn't turn them on.
Nobody except Linus expects a defconfig to boot.
I expect ./configure to give me a working tool; these *are* defaults,
and setting them *is* your responsibility as author. When it became an
in-kernel option rather than some weird distro thing, the old default
was wrong.
... Though I hadn't realized that Marco had deliberately decided to
leave support off. Surprising, since liblzma and libz seem required on
Debian anyway.
So I'm sorry Andreas: if your maintainer doesn't care about your case,
there's not much I can do :(
Subject: modules: clarify CONFIG_MODULE_COMPRESS help, suggest 'N'.
Andreas turned this option on, only to find out Debian (and Ubuntu!)
don't enable support in their kmod builds.
Shorten the text, and suggest N at the bottom (at least for now).
Reported-by: Andreas Mohr <andim2@users.sf.net>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff --git a/init/Kconfig b/init/Kconfig
index 968a001790af..bcb7e1e13f7d 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1948,26 +1948,21 @@ config MODULE_COMPRESS
bool "Compress modules on installation"
depends on MODULES
help
- This option compresses the kernel modules when 'make
- modules_install' is run.
- The modules will be compressed either using gzip or xz depend on the
- choice made in "Compression algorithm".
+ Compresses kernel modules when 'make modules_install' is run; gzip or
+ xz depending on "Compression algorithm" below.
- module-init-tools has support for gzip format while kmod handle gzip
- and xz compressed modules.
+ module-init-tools MAY support gzip, and kmod MAY support gzip and xz.
- When a kernel module is installed from outside of the main kernel
- source and uses the Kbuild system for installing modules then that
- kernel module will also be compressed when it is installed.
+ Out-of-tree kernel modules installed using Kbuild will also be
+ compressed upon installation.
- This option provides little benefit when the modules are to be used inside
- an initrd or initramfs, it generally is more efficient to compress the whole
- initrd or initramfs instead.
+ Note: for modules inside an initrd or initramfs, it's more efficient
+ to compress the whole initrd or initramfs instead.
- This is fully compatible with signed modules while the signed module is
- compressed. module-init-tools or kmod handles decompression and provide to
- other layer the uncompressed but signed payload.
+ Note: This is fully compatible with signed modules.
+
+ If in doubt, say N.
choice
prompt "Compression algorithm"
next prev parent reply other threads:[~2015-06-04 20:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 15:29 [PATCH] modules: CONFIG_MODULE_COMPRESS: add hint that userspace support may easily be missing Andreas Mohr
2015-06-01 6:26 ` Rusty Russell
2015-06-03 12:04 ` Michal Marek
2015-06-03 17:30 ` Lucas De Marchi
2015-06-03 17:36 ` Kay Sievers
2015-06-03 17:51 ` Lucas De Marchi
2015-06-04 1:30 ` Rusty Russell
2015-06-04 2:31 ` Lucas De Marchi
2015-06-04 19:53 ` Andreas Mohr
2015-06-04 20:22 ` Rusty Russell [this message]
2015-06-07 6:18 ` Lucas De Marchi
2015-06-04 2:51 ` Marco d'Itri
2015-06-04 3:19 ` Stephen Rothwell
2015-06-04 20:09 ` Andreas Mohr
2015-06-04 20:09 ` Andreas Mohr
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=87zj4fte9r.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=andi@lisas.de \
--cc=beber@meleeweb.net \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=md@linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.