public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Suzuki Poulose <suzuki@in.ibm.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [PATCH] Fix memory access errors for kexec PPC
Date: Wed, 27 Apr 2011 16:48:05 +0900	[thread overview]
Message-ID: <20110427074804.GA8738@verge.net.au> (raw)
In-Reply-To: <4DB7BA53.6040602@in.ibm.com>

On Wed, Apr 27, 2011 at 12:10:19PM +0530, Suzuki Poulose wrote:
> On 04/27/11 11:47, Simon Horman wrote:
> >On Wed, Apr 20, 2011 at 03:02:02PM +0530, Suzuki Poulose wrote:
> >>Hi,
> >>
> >>I was trying the kexec for ppc32 and came across a couple of memory errors
> >>while running with glibc.
> >>
> >>The attached patch is the outcome of the glibc's alerts !
> >>We define buf[MAXBYTES-1] and issue  fread(buf, 1, MAXBYTES, file), which glibc
> >>reports an error.
> >>
> >>Also there is a typo in the realloc_memory_ranges() code for ppc which causes in
> >>a double free().
> >
> >Thanks,
> >
> >could you please make this a formal submission by
> >supplying a Signed-off-by line?
> I have updated the patch to use realloc instead of malloc() for memory_range.

Hi,

unfortuantely this doesn't seep to apply to the current git tree.
Could you fix that?

The tree is available at
git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

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

      reply	other threads:[~2011-04-27  7:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  9:32 [PATCH] Fix memory access errors for kexec PPC Suzuki Poulose
2011-04-27  6:17 ` Simon Horman
2011-04-27  6:40   ` Suzuki Poulose
2011-04-27  7:48     ` Simon Horman [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=20110427074804.GA8738@verge.net.au \
    --to=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=suzuki@in.ibm.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