All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Michael Weiß" <michael.weiss@aisec.fraunhofer.de>
Cc: linux-man@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH] init_module.2: Document MODULE_INIT_COMPRESS_FILE flag
Date: Wed, 3 Apr 2024 11:07:45 +0200	[thread overview]
Message-ID: <Zg0Ve0E5aEG7HdEk@devuan> (raw)
In-Reply-To: <be8b4949-a304-49a4-9b88-6f02b4f556ef@aisec.fraunhofer.de>

[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]

Hi Michael,

On Tue, Apr 02, 2024 at 01:07:12PM +0200, Michael Weiß wrote:
> >>  .TP
> >>  .B EINVAL
> >>  .I flags
> >> -is invalid.
> >> +is invalid or the decompressor sanity checks failed while loading
> >> +a compressed module with flag
> >> +.BR CONFIG_MODULE_DECOMPRESS
> > 
> > This should use B, not BR.  (It uses Bold, not Bold/Roman alternating.)
> >
> I spotted another error here, too. Should be: 
> 
> 	.B MODULE_INIT_COMPRESSED_FILE
> 
> I'll fix that in v2.

Also, the two conditions seem different enough that I would split them
into two EINVAL entries.

>  
> >> +set.
> >>  .TP
> >>  .B ENOEXEC
> >>  .I fd
> >>  does not refer to an open file.
> >>  .TP
> >> +.BR EOPNOTSUPP " (since Linux 5.17)"
> >> +This error is return if the kernel was configured without
> > 
> > The first words seems redundant.  I'd use:
> > 
> > 	The kernel was configured without CONFIG_MODULE_DECOMPRESS.
> > 
> > Which seems incomplete.  I guess if the module is not compressed, then
> > it won't report this error.
> > 
> > 	The module is compressed, and the kernel was built without ...
> 
> True. But I would write:
> 
> 	The flag
> 	.B MODULE_INIT_COMPRESSED_FILE
> 	is set to load a compressed module,
> 	and the kernel was built without
> 	.BR CONFIG_MODULE_DECOMPRESS .
> 
> Since the error directly dependents on a check of the flag.

Agree.

Have a lovely day!
Alex


-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-03  9:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 12:41 [PATCH] init_module.2: Document MODULE_INIT_COMPRESS_FILE flag Michael Weiß
2024-03-30 23:05 ` Alejandro Colomar
2024-04-02 11:07   ` Michael Weiß
2024-04-03  9:07     ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-03 11:42 Michael Weiß
2024-04-04  9:01 ` Alejandro Colomar

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=Zg0Ve0E5aEG7HdEk@devuan \
    --to=alx@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=michael.weiss@aisec.fraunhofer.de \
    --cc=swboyd@chromium.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 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.