Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: Atsushi Kumagai <ats-kumagai@wm.jp.nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"dyoung@redhat.com" <dyoung@redhat.com>,
	"bhe@redhat.com" <bhe@redhat.com>
Subject: Re: [Makedumpfile Patch v2 7/7] mem-usage: allow to work only with -f for kernel version < 4.11
Date: Thu, 2 Mar 2017 11:18:00 +0530	[thread overview]
Message-ID: <ccd8139b-e5a4-3167-aa5b-94f86689767b@redhat.com> (raw)
In-Reply-To: <0910DD04CBD6DE4193FCF86B9C00BE9701EAA666@BPXM01GP.gisp.nec.co.jp>

Hi Atsushi,

On Thursday 02 March 2017 10:19 AM, Atsushi Kumagai wrote:
> Hello Pratyush,
>
>> PT_LOAD of kcore does not have valid p_paddr values for kernel version
>> less that v4.11. Therefore, older kernel will no long work for mem-usage
>> with current makedumpfile code. They can only work when they are patched
>> with fix to "update physical address for kcore ram and text".
>>
>> This patch fixes the makedumpfile so that it does not allow to work
>> older kernel for --mem-usage until someone is sure that kernel is
>> rightly patched and so uses -f in command line.
>>
>> Signed-off-by: Pratyush Anand <panand@redhat.com>
>> ---
>> makedumpfile.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/makedumpfile.c b/makedumpfile.c
>> index 3b8e9810468d..bf006ea5dd5f 100644
>> --- a/makedumpfile.c
>> +++ b/makedumpfile.c
>> @@ -11269,6 +11269,12 @@ main(int argc, char *argv[])
>> 			MSG("Try `makedumpfile --help' for more information.\n");
>> 			goto out;
>> 		}
>> +		if (info->kernel_version < KERNEL_VERSION(4, 11, 0) &&
>> +				!info->flag_force) {
>> +			MSG("mem-usage not supported for this kernel.\n");
>> +			MSG("You can try with -f if your kernel's kcore has valid p_paddr\n");
>> +			return COMPLETED;
>> +		}
>
> Should use "goto out" to prevent memory leaks since some heap blocks are
> allocated at the head of main().

OK

>
> BTW, the descriptions of -f option in man and print_usage() don't mention this usage:
>
>        -f     Force existing DUMPFILE to be overwritten.
>               Example:
>               # makedumpfile -f -d 31 -x vmlinux /proc/vmcore dumpfile
>               This command overwrites DUMPFILE even if it already exists.
>
> so they should be updated.

Does following looks fine to you?

$ makedumpfile --help | grep -A3 "\-f"
   [-f]:
       Overwrite DUMPFILE even if it already exists
       Force mem-usage to work with older kernel as well.


$ man makedumpfile | grep -w "\-f  " -A6
        -f     Force existing DUMPFILE to be overwritten and mem-usage 
to work with older kernel as well.
               Example:
               # makedumpfile -f -d 31 -x vmlinux /proc/vmcore dumpfile
               This command overwrites DUMPFILE even if it already exists.
               # makedumpfile -f --mem-usage /proc/kcore
               Kernel version lesser than v4.11 will not work with 
--mem-usage functionality until it has been  patched  with  upstream  commit
               464920104bf7.  Therefore if you have patched your older 
kernel then use -f.

Thanks for the review.

~Pratyush

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

  parent reply	other threads:[~2017-03-02  5:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  5:52 [Makedumpfile Patch v2 0/7] Fix --mem-usage /proc/kcore Pratyush Anand
2017-02-28  5:52 ` [Makedumpfile Patch v2 1/7] show_mem_usage(): calculate page offset after elf load Pratyush Anand
2017-02-28  5:52 ` [Makedumpfile Patch v2 2/7] initial(): call cach_init() a bit early Pratyush Anand
2017-02-28  5:52 ` [Makedumpfile Patch v2 3/7] x86_64: check physical address in PT_LOAD for none direct mapped regions Pratyush Anand
2017-02-28  5:52 ` [Makedumpfile Patch v2 4/7] elf_info: kcore: check for invalid physical address Pratyush Anand
2017-02-28  5:52 ` [Makedumpfile Patch v2 5/7] makedumpfile: Correct the calculation of kvaddr in set_kcore_vmcoreinfo Pratyush Anand
2017-02-28  5:52 ` [Makedumpfile Patch v2 6/7] makedumpfile: Discard process_dump_load Pratyush Anand
2017-02-28  5:52 ` [Makedumpfile Patch v2 7/7] mem-usage: allow to work only with -f for kernel version < 4.11 Pratyush Anand
2017-03-02  4:49   ` Atsushi Kumagai
2017-03-02  5:47     ` Pratyush Anand
2017-03-02  5:48     ` Pratyush Anand [this message]
2017-03-02  7:29       ` Atsushi Kumagai
2017-02-28 15:05 ` [Makedumpfile Patch v2 0/7] Fix --mem-usage /proc/kcore Pratyush Anand

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=ccd8139b-e5a4-3167-aa5b-94f86689767b@redhat.com \
    --to=panand@redhat.com \
    --cc=ats-kumagai@wm.jp.nec.com \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.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