From: Song Liu <songliubraving@meta.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Song Liu <song@kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>, Kernel Team <kernel-team@meta.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v10] module: replace module_layout with module_memory
Date: Thu, 9 Feb 2023 00:16:46 +0000 [thread overview]
Message-ID: <70DCC6C0-53E2-4C18-B147-B2F600C66E54@fb.com> (raw)
In-Reply-To: <b40ec330-8c9e-0265-19b9-d82b516c95c1@csgroup.eu>
> On Feb 8, 2023, at 9:48 AM, Christophe Leroy <christophe.leroy@csgroup.eu> wrote:
[...]
>> {
>> unsigned long min = (unsigned long)base;
>> unsigned long max = min + size;
>>
>> +#ifdef CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC
>
> A #ifdef shouldn't be required. You can use IS_ENABLED() instead:
>
>
>
>> + if (mod_mem_type_is_core_data(type)) {
>
> if (IS_ENABLED(CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC) &&
> mod_mem_type_is_core_data(type))
>
>> + if (min < tree->data_addr_min)
>> + tree->data_addr_min = min;
>> + if (max > tree->data_addr_max)
>> + tree->data_addr_max = max;
>> + return;
>> + }
>> +#endif
To use IS_ENABLED() here, we also need to keep data_addr_[min|max]
around. Do we really want them?
Btw, we will think about all these details again with the type aware
module_alloc().
[...]
>>
>> +
>> +static void free_mod_mem(struct module *mod)
>> +{
>> + /* free the memory in the right order to avoid use-after-free */
>
> Instead of 'right order', explain what the right order is.
> As far as I understand it is only to free MOD_DATA last. Everything else
> doesn't matter.
I rewrote the function as:
static void free_mod_mem(struct module *mod)
{
for_each_mod_mem_type(type) {
struct module_memory *mod_mem = &mod->mem[type];
/* free MOD_DATA at the end, as it hosts mod */
if (type == MOD_DATA)
continue;
/* Free lock-classes; relies on the preceding sync_rcu(). */
lockdep_free_key_range(mod_mem->base, mod_mem->size);
if (mod_mem->size)
module_memory_free(mod_mem->base, type);
}
/* free MOD_DATA at the end, as it hosts mod */
lockdep_free_key_range(mod->mem[MOD_DATA].base, mod->mem[MOD_DATA].size);
module_memory_free(mod->mem[MOD_DATA].base, MOD_DATA);
}
Does this look good?
Thanks,
Song
[...]
next prev parent reply other threads:[~2023-02-09 0:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 0:28 [PATCH v10] module: replace module_layout with module_memory Song Liu
2023-02-07 22:19 ` Song Liu
2023-02-08 8:37 ` Thomas Gleixner
2023-02-08 16:06 ` Luis Chamberlain
2023-02-08 17:48 ` Christophe Leroy
2023-02-08 21:39 ` Song Liu
2023-02-09 6:32 ` Christophe Leroy
2023-02-09 0:16 ` Song Liu [this message]
2023-02-09 6:37 ` Christophe Leroy
2023-02-09 17:28 ` Song Liu
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=70DCC6C0-53E2-4C18-B147-B2F600C66E54@fb.com \
--to=songliubraving@meta.com \
--cc=christophe.leroy@csgroup.eu \
--cc=hch@lst.de \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
/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