From: Aruna Balakrishnaiah <arunabal@linux.vnet.ibm.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: tachibana@mxm.nes.nec.co.jp, kexec@lists.infradead.org,
aruna@linux.vnet.ibm.com
Subject: Re: [PATCH] Fix segmentation fault for makedumpfile -x/--split
Date: Thu, 23 Feb 2012 16:12:48 +0530 [thread overview]
Message-ID: <4F461828.8020601@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120223183505.2ab30cfd.kumagai-atsushi@mxc.nes.nec.co.jp>
On Thursday 23 February 2012 03:05 PM, Atsushi Kumagai wrote:
Hi Atsushi,
> Hi Aruna,
>
> On Wed, 1 Feb 2012 13:15:18 +0900
> Atsushi Kumagai<kumagai-atsushi@mxc.nes.nec.co.jp> wrote:
>
>> Hi Aruna,
>>
>> On Tue, 31 Jan 2012 15:56:33 +0530
>> Aruna Balakrishnaiah<aruna@linux.vnet.ibm.com> wrote:
>>
>>> The patch fixes the segmentation fault issue of makedumpfile when a
>>> user specifies an invalid file name with -x/--split option.
>>> The patch takes care of such a scenario by setting .find_debuginfo to
>>> a function pointer which returns -1 and throws error messages against
>>> invalid vmlinux file input. With a valid vmlinux file .find_debuginfo
>>> was never invoked since the absolute path of debuginfo was known by the
>>> time we call init_dwarf_info.
>>>
>>> Signed-off-by: Aruna Balakrishnaiah<aruna@linux.vnet.ibm.com>
>>> ---
>>> dwarf_info.c | 25 +++++++++++++++++++++++++
>>> 1 files changed, 25 insertions(+), 0 deletions(-)
> I'm reviewing your patch and it looks good.
>
> However, I can't guess that the segmentation fault caused
> by --split option because --split option doesn't require an argument.
>
> Would you tell me the case that you thought.
This is the case,
makedumpfile --split -x /boot/vmlinuz vmcore vm1 vm2
when used compressed vmlinux with -x.
Thanks,
Aruna
> Thanks
> Atsushi Kumagai
>
--
Regards,
Aruna Balakrishnaiah<aruna@linux.vnet.ibm.com>
Linux Technology Center,
IBM India Systems and Technology Lab
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-02-23 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 10:26 [PATCH] Fix segmentation fault for makedumpfile -x/--split Aruna Balakrishnaiah
2012-02-01 4:15 ` Atsushi Kumagai
2012-02-23 9:35 ` Atsushi Kumagai
2012-02-23 10:42 ` Aruna Balakrishnaiah [this message]
2012-02-24 3:05 ` Atsushi Kumagai
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=4F461828.8020601@linux.vnet.ibm.com \
--to=arunabal@linux.vnet.ibm.com \
--cc=aruna@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=tachibana@mxm.nes.nec.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.