From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: kumagai-atsushi@mxc.nes.nec.co.jp
Cc: ptesarik@suse.cz, kexec@lists.infradead.org
Subject: Re: [PATCH 0/2] cache: fix cache logic not go into invalid state
Date: Thu, 19 Sep 2013 09:53:37 +0900 [thread overview]
Message-ID: <523A4B11.6010409@jp.fujitsu.com> (raw)
In-Reply-To: <20130917062606.4671.40617.stgit@localhost6.localdomain6>
Hello Kumagai-san,
Could you review these patches?
(2013/09/17 15:29), HATAYAMA Daisuke wrote:
> I faced failure of sadump phys_base calculation and found a bug in
> cache.c causes it. Due to the bug, cache_alloc() returns NULL forever
> throughout execution. The fix is the 2nd patch. During the
> investigation I also found a lack of malloc() allocation failure
> check. The fix is the 1st patch. Primary is the 2nd one.
>
> I built this patch set on top of devel branch.
>
> ---
>
> HATAYAMA Daisuke (2):
> cache: allocate buffers at initialization to detect malloc() failure
> cache: reuse entry in pending list
>
>
> cache.c | 50 +++++++++++++++++++++++++++++++++-----------------
> cache.h | 1 +
> makedumpfile.c | 3 +++
> 3 files changed, 37 insertions(+), 17 deletions(-)
>
--
Thanks.
HATAYAMA, Daisuke
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-09-19 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 6:29 [PATCH 0/2] cache: fix cache logic not go into invalid state HATAYAMA Daisuke
2013-09-17 6:29 ` [PATCH 1/2] cache: allocate buffers at initialization to detect malloc() failure HATAYAMA Daisuke
2013-09-17 6:29 ` [PATCH 2/2] cache: reuse entry in pending list HATAYAMA Daisuke
2013-09-19 0:53 ` HATAYAMA Daisuke [this message]
2013-09-19 8:18 ` [PATCH 0/2] cache: fix cache logic not go into invalid state 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=523A4B11.6010409@jp.fujitsu.com \
--to=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=ptesarik@suse.cz \
/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.