Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Roberts <ryan.roberts@arm.com>
To: Baoquan He <bhe@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	David Hildenbrand <david@redhat.com>,
	Greg Marsden <greg.marsden@oracle.com>,
	Ivan Ivanov <ivan.ivanov@suse.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	Marc Zyngier <maz@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Matthias Brugger <mbrugger@suse.com>,
	Miroslav Benes <mbenes@suse.cz>, Will Deacon <will@kernel.org>,
	kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH v1 19/57] crash: Remove PAGE_SIZE compile-time constant assumption
Date: Tue, 15 Oct 2024 12:13:55 +0100	[thread overview]
Message-ID: <2e561511-ab20-4aa9-9b92-bd6ac6678087@arm.com> (raw)
In-Reply-To: <Zw3luHGG3LqHge2m@MiWiFi-R3L-srv>

On 15/10/2024 04:47, Baoquan He wrote:
> On 10/14/24 at 11:58am, Ryan Roberts wrote:
>> To prepare for supporting boot-time page size selection, refactor code
>> to remove assumptions about PAGE_SIZE being compile-time constant. Code
>> intended to be equivalent when compile-time page size is active.
>>
>> Updated BUILD_BUG_ON() to test against limit.
>>
>> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
>> ---
>>
>> ***NOTE***
>> Any confused maintainers may want to read the cover note here for context:
>> https://lore.kernel.org/all/20241014105514.3206191-1-ryan.roberts@arm.com/
>>
>>  kernel/crash_core.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
>> index 63cf89393c6eb..978c600a47ac8 100644
>> --- a/kernel/crash_core.c
>> +++ b/kernel/crash_core.c
>> @@ -465,7 +465,7 @@ static int __init crash_notes_memory_init(void)
>>  	 * Break compile if size is bigger than PAGE_SIZE since crash_notes
>>  	 * definitely will be in 2 pages with that.
>>  	 */
>> -	BUILD_BUG_ON(size > PAGE_SIZE);
>> +	BUILD_BUG_ON(size > PAGE_SIZE_MIN);
> 
> This should be OK. While one thing which could happen is if selected size
> is 64K, PAGE_SIZE_MIN is 4K, it will issue a false-positive warning when
> compiling while actual it's not a problem during running. 

PAGE_SIZE can only ever be bigger than PAGE_SIZE_MIN if compiling a "boot-time
page size" build. And in this case, you need to know that size is small enough
to work with any of the boot-time selectable page sizes. Since size
(=sizeof(note_buf_t)) is invariant to PAGE_SIZE, we can do this by checking
against PAGE_SIZE_MIN.

So I don't think this could ever lead to a false-positive.


Not sure if
> that could happen on arm64. Anyway, we can check the crash_notes to get
> why it's so big when it really happens. So,
> 
> Acked-by: Baoquan He <bhe@redhat.com>

Thanks!

> 
>>  
>>  	crash_notes = __alloc_percpu(size, align);
>>  	if (!crash_notes) {
>> -- 
>> 2.43.0
>>
>>
> 


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2024-10-15 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241014105514.3206191-1-ryan.roberts@arm.com>
     [not found] ` <20241014105912.3207374-1-ryan.roberts@arm.com>
2024-10-14 10:58   ` [RFC PATCH v1 19/57] crash: Remove PAGE_SIZE compile-time constant assumption Ryan Roberts
2024-10-15  3:47     ` Baoquan He
2024-10-15 11:13       ` Ryan Roberts [this message]
2024-10-18  3:00         ` Baoquan He

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=2e561511-ab20-4aa9-9b92-bd6ac6678087@arm.com \
    --to=ryan.roberts@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=bhe@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=greg.marsden@oracle.com \
    --cc=ivan.ivanov@suse.com \
    --cc=kaleshsingh@google.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mbrugger@suse.com \
    --cc=will@kernel.org \
    /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