From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Michael Ellerman <mpe@ellerman.id.au>,
Andrew Morton <akpm@linux-foundation.org>,
arnd@arndb.de
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-s390@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arch@vger.kernel.org,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Subject: Re: [PATCH 1/3] mm: Make generic arch_is_kernel_initmem_freed() do what it says
Date: Mon, 27 Sep 2021 15:51:09 +0200 [thread overview]
Message-ID: <f206b856-f5a8-3e47-03cb-49aaa5c521f0@csgroup.eu> (raw)
In-Reply-To: <87h7e6kvs3.fsf@mpe.ellerman.id.au>
Le 27/09/2021 à 15:11, Michael Ellerman a écrit :
> Christophe Leroy <christophe.leroy@csgroup.eu> writes:
>> Commit 7a5da02de8d6 ("locking/lockdep: check for freed initmem in
>> static_obj()") added arch_is_kernel_initmem_freed() which is supposed
>> to report whether an object is part of already freed init memory.
>>
>> For the time being, the generic version of arch_is_kernel_initmem_freed()
>> always reports 'false', allthough free_initmem() is generically called
>> on all architectures.
>>
>> Therefore, change the generic version of arch_is_kernel_initmem_freed()
>> to check whether free_initmem() has been called. If so, then check
>> if a given address falls into init memory.
>>
>> In order to use function init_section_contains(), the fonction is
>> moved at the end of asm-generic/section.h
>>
>> Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
>> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>> ---
>> include/asm-generic/sections.h | 31 +++++++++++++++++--------------
>> 1 file changed, 17 insertions(+), 14 deletions(-)
>>
>> diff --git a/include/asm-generic/sections.h b/include/asm-generic/sections.h
>> index d16302d3eb59..d1e5bb2c6b72 100644
>> --- a/include/asm-generic/sections.h
>> +++ b/include/asm-generic/sections.h
>> @@ -172,4 +158,21 @@ static inline bool is_kernel_rodata(unsigned long addr)
>> addr < (unsigned long)__end_rodata;
>> }
>>
>> +/*
>> + * Check if an address is part of freed initmem. This is needed on architectures
>> + * with virt == phys kernel mapping, for code that wants to check if an address
>> + * is part of a static object within [_stext, _end]. After initmem is freed,
>> + * memory can be allocated from it, and such allocations would then have
>> + * addresses within the range [_stext, _end].
>> + */
>> +#ifndef arch_is_kernel_initmem_freed
>> +static inline int arch_is_kernel_initmem_freed(unsigned long addr)
>> +{
>> + if (system_state < SYSTEM_RUNNING)
>> + return 0;
>> +
>> + return init_section_contains((void *)addr, 1);
>> +}
>> +#endif
>
> This will return an incorrect result for a short period during boot
> won't it?
>
> See init/main.c:
>
> static int __ref kernel_init(void *unused)
> {
> ...
> free_initmem(); <- memory is freed here
> mark_readonly();
>
> /*
> * Kernel mappings are now finalized - update the userspace page-table
> * to finalize PTI.
> */
> pti_finalize();
>
> system_state = SYSTEM_RUNNING;
>
>
> After free_initmem() we have address ranges that are now freed initmem,
> but arch_is_kernel_initmem_freed() continues to return 0 (false) for all
> addresses, until we update system_state.
>
> Possibly that doesn't matter for any of the current callers, but it
> seems pretty dicey to me.
>
Yes I saw it but as function core_kernel_text() uses that criteria for
deciding whether a given init text address is valid or not, I thought it
was just ok.
Should we add an intermediate state called for exemple
SYSTEM_FREEING_INIT just before SYSTEM_RUNNING ?
Christophe
prev parent reply other threads:[~2021-09-27 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 13:48 [PATCH 1/3] mm: Make generic arch_is_kernel_initmem_freed() do what it says Christophe Leroy
2021-09-24 13:48 ` [PATCH 2/3] powerpc: Use generic version of arch_is_kernel_initmem_freed() Christophe Leroy
2021-09-24 13:48 ` [PATCH 3/3] s390: " Christophe Leroy
2021-09-27 13:11 ` [PATCH 1/3] mm: Make generic arch_is_kernel_initmem_freed() do what it says Michael Ellerman
2021-09-27 13:51 ` Christophe Leroy [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=f206b856-f5a8-3e47-03cb-49aaa5c521f0@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gerald.schaefer@linux.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 NNTP newsgroup(s).