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 v3 4/4] module: separate vermagic and livepatch checks
Date: Mon, 1 Sep 2025 11:34:06 +0200 [thread overview]
Message-ID: <919b4262-37aa-4cde-a2dd-ebdf553178f4@suse.com> (raw)
In-Reply-To: <20250829084927.156676-5-wangjinchao600@gmail.com>
On 8/29/25 10:49 AM, Jinchao Wang wrote:
> Rename check_modinfo() to check_modinfo_vermagic() to clarify it only
> checks vermagic compatibility.
>
> Move livepatch check to happen after vermagic check in early_mod_check(),
> creating proper separation of concerns.
> No functional changes, just clearer code organization.
>
> Signed-off-by: Jinchao Wang <wangjinchao600@gmail.com>
Reviewed-by: Petr Pavlu <petr.pavlu@suse.com>
--
Thanks,
Petr
prev parent reply other threads:[~2025-09-01 9:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 8:49 [PATCH v3 0/4] module: logging and code improvements Jinchao Wang
2025-08-29 8:49 ` [PATCH v3 1/4] module: signing: Use pr_err for signature rejection Jinchao Wang
2025-09-01 9:25 ` Petr Pavlu
2025-09-01 18:18 ` Daniel Gomez
2025-09-02 1:57 ` Jinchao Wang
2025-08-29 8:49 ` [PATCH v3 2/4] module: show why force load fails Jinchao Wang
2025-09-01 9:26 ` Petr Pavlu
2025-09-01 18:29 ` Daniel Gomez
2025-09-02 2:06 ` Jinchao Wang
2025-08-29 8:49 ` [PATCH v3 3/4] module: centralize no-versions force load check Jinchao Wang
2025-09-01 9:30 ` Petr Pavlu
2025-08-29 8:49 ` [PATCH v3 4/4] module: separate vermagic and livepatch checks Jinchao Wang
2025-09-01 9:34 ` Petr Pavlu [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=919b4262-37aa-4cde-a2dd-ebdf553178f4@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®