From: Daniel Gomez <da.gomez@samsung.com>
To: Matthew Maurer <mmaurer@google.com>, <masahiroy@kernel.org>,
<ndesaulniers@google.com>, <ojeda@kernel.org>, <gary@garyguo.net>,
<mcgrof@kernel.org>, Alex Gaynor <alex.gaynor@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, neal@gompa.dev, marcan@marcan.st,
j@jannau.net, asahi@lists.linux.dev,
"Petr Pavlu" <petr.pavlu@suse.com>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-modules@vger.kernel.org
Subject: Re: [PATCH v4 01/16] module: Take const arg in validate_section_offset
Date: Wed, 25 Sep 2024 11:00:28 +0200 [thread overview]
Message-ID: <d56f36da-afd9-4956-8b74-8b0b17baadf2@samsung.com> (raw)
In-Reply-To: <20240924212024.540574-2-mmaurer@google.com>
On 9/24/2024 11:19 PM, Matthew Maurer wrote:
> `validate_section_offset` doesn't modify the info passed in. Make this
> clear by adjusting the type signature.
>
> Signed-off-by: Matthew Maurer <mmaurer@google.com>
> ---
> kernel/module/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/module/main.c b/kernel/module/main.c
> index 49b9bca9de12..1a2dd52147ba 100644
> --- a/kernel/module/main.c
> +++ b/kernel/module/main.c
> @@ -1645,7 +1645,7 @@ bool __weak module_exit_section(const char *name)
> return strstarts(name, ".exit");
> }
>
> -static int validate_section_offset(struct load_info *info, Elf_Shdr *shdr)
> +static int validate_section_offset(const struct load_info *info, Elf_Shdr *shdr)
> {
> #if defined(CONFIG_64BIT)
> unsigned long long secend;
The cover letter is missing a From/Cc to the linux-modules list. So I
was missing the context here. Looking at lore I found it here:
https://lore.kernel.org/asahi/20240924212024.540574-1-mmaurer@google.com/
Can you add linux-modules list in case there's a next revision?
Also, the cover letter is missing a full changelog other than a
reference to the previous discussions and to the last changes.
Daniel
next prev parent reply other threads:[~2024-09-25 9:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 21:19 [PATCH v4 00/16] Extended MODVERSIONS Support Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 01/16] module: Take const arg in validate_section_offset Matthew Maurer
2024-09-25 9:00 ` Daniel Gomez [this message]
2024-09-24 21:19 ` [PATCH v4 02/16] module: Factor out elf_validity_ehdr Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 03/16] module: Factor out elf_validity_cache_sechdrs Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 04/16] module: Factor out elf_validity_cache_secstrings Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 05/16] module: Factor out elf_validity_cache_index_info Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 06/16] module: Factor out elf_validity_cache_index_mod Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 07/16] module: Factor out elf_validity_cache_index_sym Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 08/16] module: Factor out elf_validity_cache_index_str Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 09/16] module: Group section index calculations together Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 10/16] module: Factor out elf_validity_cache_strtab Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 11/16] module: Additional validation in elf_validity_cache_strtab Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 12/16] module: Reformat struct for code style Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 13/16] export_report: Rehabilitate script Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 14/16] modules: Support extended MODVERSIONS info Matthew Maurer
2024-09-25 23:00 ` Sami Tolvanen
2024-09-25 23:42 ` Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 15/16] modpost: Produce extended modversion information Matthew Maurer
2024-09-24 21:19 ` [PATCH v4 16/16] export_report: Use new version info format Matthew Maurer
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=d56f36da-afd9-4956-8b74-8b0b17baadf2@samsung.com \
--to=da.gomez@samsung.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=asahi@lists.linux.dev \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=j@jannau.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mmaurer@google.com \
--cc=ndesaulniers@google.com \
--cc=neal@gompa.dev \
--cc=ojeda@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=tmgross@umich.edu \
/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