From: Petr Pavlu <petr.pavlu@suse.com>
To: Jinchao Wang <wangjinchao600@gmail.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] module: centralize no-versions force load check
Date: Tue, 26 Aug 2025 11:40:39 +0200 [thread overview]
Message-ID: <14e0f072-59e6-4657-8ab1-fe1fbc30ac43@suse.com> (raw)
In-Reply-To: <20250825091545.18607-4-wangjinchao600@gmail.com>
On 8/25/25 11:15 AM, Jinchao Wang wrote:
> Move try_to_force_load() call from check_version() to
> check_modstruct_version() to handle "no versions" case only once before
> other version checks.
>
> This prevents duplicate force load attempts and makes the error message
> show the proper reason.
>
> Signed-off-by: Jinchao Wang <wangjinchao600@gmail.com>
> ---
> kernel/module/version.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/module/version.c b/kernel/module/version.c
> index 2beefeba82d9..3f07fd03cb30 100644
> --- a/kernel/module/version.c
> +++ b/kernel/module/version.c
> @@ -41,10 +41,6 @@ int check_version(const struct load_info *info,
> return 1;
> }
>
> - /* No versions at all? modprobe --force does this. */
> - if (versindex == 0)
> - return try_to_force_load(mod, symname) == 0;
> -
> versions = (void *)sechdrs[versindex].sh_addr;
> num_versions = sechdrs[versindex].sh_size
> / sizeof(struct modversion_info);
Removing this return completely means that when versindex == 0, the
function incorrectly looks at the dummy section #0 and eventually
calls pr_warn_once("%s: no symbol version for %s\n", ...).
As I outlined in my prototype patch previously [1], I think this should
be changed to:
/* No versions? Ok, already tainted in check_modstruct_version(). */
if (versindex == 0)
return 1;
> @@ -81,6 +77,11 @@ int check_modstruct_version(const struct load_info *info,
> };
> bool have_symbol;
>
> + /* No versions at all? modprobe --force does this. */
> + if (info->index.vers == 0 &&
> + try_to_force_load(mod, "no versions module"))
> + return 1;
> +
> /*
> * Since this should be found in kernel (which can't be removed), no
> * locking is necessary. Regardless use a RCU read section to keep
I suggest that the reason message should say "no versions for imported
symbols" to indicate which version data is missing and to be consistent
with check_export_symbol_versions(), which uses "no versions for
exported symbols".
[1] https://lore.kernel.org/linux-modules/3992b57d-3d8b-4d60-bc4a-f227f712dcca@suse.com/
--
Thanks,
Petr
next prev parent reply other threads:[~2025-08-26 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 9:15 [PATCH v2 0/4] module: logging and code improvements Jinchao Wang
2025-08-25 9:15 ` [PATCH v2 1/4] module: signing: Use pr_err for signature rejection Jinchao Wang
2025-08-25 9:15 ` [PATCH v2 2/4] module: show why force load fails Jinchao Wang
2025-08-26 9:33 ` Petr Pavlu
2025-08-26 9:51 ` Jinchao Wang
2025-08-25 9:15 ` [PATCH v2 3/4] module: centralize no-versions force load check Jinchao Wang
2025-08-26 9:40 ` Petr Pavlu [this message]
2025-08-25 9:15 ` [PATCH v2 4/4] module: separate vermagic and livepatch checks Jinchao Wang
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=14e0f072-59e6-4657-8ab1-fe1fbc30ac43@suse.com \
--to=petr.pavlu@suse.com \
--cc=da.gomez@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=samitolvanen@google.com \
--cc=wangjinchao600@gmail.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
all inboxes | Powered by JetHome®