linux-kernel - Re: [PATCH] mips: kernel: setup: fix crash kernel resource allocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210208131714.GA4740@ikhorn>
Date:   Mon, 8 Feb 2021 15:17:15 +0200
From:   Ivan Khoronzhuk <ivan.khoronzhuk@...il.com>
To:     Jinyang He <hejinyang@...ngson.cn>
Cc:     Ivan Khoronzhuk <ikhoronz@...co.com>, linux-mips@...r.kernel.org,
        tsbogend@...ha.franken.de, linux-kernel@...r.kernel.org,
        yangtiezhu@...ngson.cn, rppt@...nel.org
Subject: Re: [PATCH] mips: kernel: setup: fix crash kernel resource allocation

On Sun, Feb 07, 2021 at 11:19:03AM +0800, Jinyang He wrote:
>On 02/06/2021 08:59 PM, Ivan Khoronzhuk wrote:
>
>>In order to avoid crash kernel corruption, its memory is reserved
>>early in memblock and as result, in time when resources are inited
>>it's not present in memblock.memory, so crash kernel memory is out
>>of ranges listed with for_each_mem_range(). To avoid it and still
>>keep memory reserved lets reseve it out of loop by inserting it in
>>iomem_resource.
>
>Hi, Ivan,
>
>I'm not familiar with memblock. If the following my ideas show my
>ignorance, please forgive me.
>
>First, not only the crash kernel is reserved early in memblock, but also
>code, data, and bss are also reserved in bootmem_init():
>
>    /* Reserve memory occupied by kernel. */
>    memblock_reserve(__pa_symbol(&_text),
>            __pa_symbol(&_end) - __pa_symbol(&_text));
>
>(CONFIG_NUMA is not enabled. NUMA platform reserved them is earlier.)
>
>If there is something unsuitable with the crash kernel, is there something
>unsuitable with the kernel memory?
>
>
>Then, for_each_mem_range() is normal memory. Although memblock_reserve()
>has used before that, it just adds memory to memblock.reserved. That means
>it will still appear in memblock.memory. Thus, here I have a question,
>do we need to use replace for_each_mem_range with for_each_mem_range_rev?

Reserve doesn't mean it's present in memblock.memory, if it memory was not
added before, like it's supposed. In my canse, seems like to local issue it
wasn't, that's why it was not present. So, traverse direction won't solve
this obviously.

>
>Finally, thank you for the patch, it makes me think a lot.
>
>Thanks,
>Jinyang
>
>>Fixes: a94e4f24ec83 ("MIPS: init: Drop boot_mem_map")
>>Signed-off-by: Ivan Khoronzhuk <ikhoronz@...co.com>
>>---
>>Based on linux-next/master
>>
>>  arch/mips/kernel/setup.c | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>>diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
>>index 3785c72bc3bc..25e376ef2f2a 100644
>>--- a/arch/mips/kernel/setup.c
>>+++ b/arch/mips/kernel/setup.c
>>@@ -473,14 +473,15 @@ static void __init mips_parse_crashkernel(void)
>>  	crashk_res.end	 = crash_base + crash_size - 1;
>>  }
>>-static void __init request_crashkernel(struct resource *res)
>>+static void __init request_crashkernel(void)
>>  {
>>  	int ret;
>>  	if (crashk_res.start == crashk_res.end)
>>  		return;
>>-	ret = request_resource(res, &crashk_res);
>>+	/* The crashk resource shoud be located in normal mem */
>>+	ret = insert_resource(&iomem_resource, &crashk_res);
>>  	if (!ret)
>>  		pr_info("Reserving %ldMB of memory at %ldMB for crashkernel\n",
>>  			(unsigned long)(resource_size(&crashk_res) >> 20),
>>@@ -734,8 +735,9 @@ static void __init resource_init(void)
>>  		request_resource(res, &code_resource);
>>  		request_resource(res, &data_resource);
>>  		request_resource(res, &bss_resource);
>>-		request_crashkernel(res);
>>  	}
>>+
>>+	request_crashkernel();
>>  }
>>  #ifdef CONFIG_SMP
>

-- 
Regards,
Ivan Khoronzhuk