From: Xishi Qiu <qiuxishi@huawei.com>
To: Matt Fleming <matt.fleming@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
fenghua.yu@intel.com, Liujiang <jiang.liu@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-efi@vger.kernel.org, linux-mm@kvack.org,
Hanjun Guo <guohanjun@huawei.com>,
WuJianguo <wujianguo@huawei.com>
Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Sat, 16 Feb 2013 09:55:44 +0800 [thread overview]
Message-ID: <511EE720.6060907@huawei.com> (raw)
In-Reply-To: <1360750028.24917.28.camel@mfleming-mobl1.ger.corp.intel.com>
On 2013/2/13 18:07, Matt Fleming wrote:
>> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M"
>> and use sparse memory model, when crash kernel booting it changes [128M-728M] to [128M-720M].
>> But initrd memory is in [709M-727M], and virt_addr_valid() *can not* check the invalid pages
>> when freeing initrd memory. There are some pages missed at the end of the seciton.
>>
>> ChangeLog V3:
>> fixed vaddr mistake
>> ChangeLog V2:
>> add invalid pages check when freeing initrd memory
>>
>> Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
>> ---
>> arch/ia64/mm/init.c | 4 ++++
>> 1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/ia64/mm/init.c b/arch/ia64/mm/init.c
>> index 082e383..8a269f8 100644
>> --- a/arch/ia64/mm/init.c
>> +++ b/arch/ia64/mm/init.c
>> @@ -173,6 +173,7 @@ void __init
>> free_initrd_mem (unsigned long start, unsigned long end)
>> {
>> struct page *page;
>> + unsigned long pfn;
>> /*
>> * EFI uses 4KB pages while the kernel can use 4KB or bigger.
>> * Thus EFI and the kernel may have different page sizes. It is
>> @@ -213,6 +214,9 @@ free_initrd_mem (unsigned long start, unsigned long end)
>> for (; start < end; start += PAGE_SIZE) {
>> if (!virt_addr_valid(start))
>> continue;
>> + pfn = __pa(start) >> PAGE_SHIFT;
>> + if (pfn >= max_low_pfn)
>> + continue;
>> page = virt_to_page(start);
>> ClearPageReserved(page);
>> init_page_count(page);
>
> I would have presumed that fixing this bug would involve modifying the
> ia64-specific kexec code?
>
> Tony, Fenghua? Any thoughts?
Hi, I had the Spring Festival a few days ago. Please ignore the earlier
patch and consider the V3 one above.
Thanks,
Xishi Qiu
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-02-16 1:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 3:52 [PATCH] ia64/mm: fix a bad_page bug when crash kernel booting Xishi Qiu
2013-02-04 16:32 ` Matt Fleming
2013-02-05 3:48 ` Xishi Qiu
2013-02-07 2:32 ` [PATCH V2] " Xishi Qiu
2013-02-07 6:09 ` [PATCH V3] " Xishi Qiu
2013-02-13 0:11 ` Tony Luck
2013-02-13 0:19 ` Andrew Morton
2013-02-13 0:32 ` Tony Luck
2013-02-13 0:22 ` Andrew Morton
2013-02-13 10:07 ` Matt Fleming
2013-02-16 1:55 ` Xishi Qiu [this message]
2013-02-19 21:38 ` Luck, Tony
2013-02-19 21:56 ` Tony Luck
2013-02-20 1:38 ` Xishi Qiu
2013-02-21 18:21 ` Tony Luck
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=511EE720.6060907@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=guohanjun@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matt.fleming@intel.com \
--cc=tony.luck@intel.com \
--cc=wujianguo@huawei.com \
/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).