From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: linux-modules@vger.kernel.org, Dmitry Antipov <dmantipov@yandex.ru>
Cc: Lucas De Marchi <lucas.de.marchi@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH] libkmod, depmod: prefer -ENODATA over -ENOENT if no section found
Date: Tue, 30 May 2023 12:55:44 -0700 [thread overview]
Message-ID: <168547650089.426113.5608177932648633484.b4-ty@gmail.com> (raw)
In-Reply-To: <20230519093630.474185-1-dmantipov@yandex.ru>
On Fri, 19 May 2023 12:36:30 +0300, Dmitry Antipov wrote:
> When the module is definitely present but CONFIG_MODVERSIONS is
> disabled, the following error message may be somewhat confusing:
>
> modprobe --dump-modversions /path/to/module.ko.xz
> modprobe: FATAL: could not get modversions of /path/to/module.ko.xz: No such file or directory
>
> Choosing among the convenient errno values, I would suggest to use
> ENODATA when the module lacks a particular ELF section (and vermagic
> as well). So now it is expected to be:
>
> [...]
Applied, thanks!
[1/1] libkmod, depmod: prefer -ENODATA over -ENOENT if no section found
commit: 5c004af29daf38119cc472dc8f1f080f10da6d82
Best regards,
--
Lucas De Marchi <lucas.de.marchi@gmail.com>
prev parent reply other threads:[~2023-05-30 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 5:47 [PATCH] modprobe: prefer -ENODATA over -ENOENT if no section found Dmitry Antipov
2023-05-19 6:52 ` Christophe Leroy
2023-05-19 7:03 ` Dmitry Antipov
2023-05-19 7:06 ` Christophe Leroy
2023-05-19 7:28 ` [PATCH] libkmod: " Dmitry Antipov
2023-05-19 9:36 ` [PATCH] libkmod, depmod: " Dmitry Antipov
2023-05-30 19:55 ` Lucas De Marchi [this message]
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=168547650089.426113.5608177932648633484.b4-ty@gmail.com \
--to=lucas.de.marchi@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dmantipov@yandex.ru \
--cc=linux-modules@vger.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).