From: Jingbai Ma <jingbai.ma@hp.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: kexec@lists.infradead.org, kumagai-atsushi@mxc.nes.nec.co.jp,
jingbai.ma@hp.com
Subject: Re: [BUG] makedumpfile v1.5.5
Date: Fri, 28 Mar 2014 20:31:48 +0800 [thread overview]
Message-ID: <53356BB4.4010001@hp.com> (raw)
In-Reply-To: <20140327.022032.54368351.d.hatayama@jp.fujitsu.com>
On 03/27/2014 09:20 AM, HATAYAMA Daisuke wrote:
>
> Sorry. This was fixed by the following patch.
>
> commit 4404368a0860e3b6c845eb41782e97a9bf7593b8
> Author: WANG Chao <chaowang@redhat.com>
> Date: Wed Dec 18 22:34:43 2013 +0900
>
> [PATCH] memset() in cyclic bitmap initialization introduce segment fault.
>
> Thanks.
> HATAYAMA, Daisuke
>
I have applied this patch, the problem still exists, so I investigated
on it a bit more, I found the root cause.
I have sent a patch to fix it:
http://lists.infradead.org/pipermail/kexec/2014-March/011408.html
--
Thanks,
Jingbai Ma
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-03-28 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 11:09 [BUG] makedumpfile v1.5.5 Jingbai Ma
2014-03-27 1:20 ` HATAYAMA Daisuke
2014-03-28 12:31 ` Jingbai Ma [this message]
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=53356BB4.4010001@hp.com \
--to=jingbai.ma@hp.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox