From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mm: fix invalid loop for poison_init_mem
Date: Wed, 03 Aug 2011 09:44:41 -0700 [thread overview]
Message-ID: <4E397AF9.8070702@codeaurora.org> (raw)
In-Reply-To: <1312385728-27311-1-git-send-email-jamie@jamieiles.com>
On 08/03/2011 08:35 AM, Jamie Iles wrote:
> poison_init_mem() used a loop of:
>
> while ((count = count - 4))
>
> which has 2 problems - an off by one error so that we do one less word
> than we should, and the other is that if count == 0 then we loop forever
> and poison too much. On a platform with HAVE_TCM=y but nothing in the
> TCM's, this caused corruption and the platform failed to boot.
>
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
>
> Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Jamie Iles <jamie@jamieiles.com>
> ---
> arch/arm/mm/init.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
> index 2fee782..91bca35 100644
> --- a/arch/arm/mm/init.c
> +++ b/arch/arm/mm/init.c
> @@ -441,7 +441,7 @@ static inline int free_area(unsigned long pfn, unsigned long end, char *s)
> static inline void poison_init_mem(void *s, size_t count)
> {
> u32 *p = (u32 *)s;
> - while ((count = count - 4))
> + for (; count != 0; count -= 4)
> *p++ = 0xe7fddef0;
> }
>
Now where's that bag...
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2011-08-03 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 15:35 [PATCH] mm: fix invalid loop for poison_init_mem Jamie Iles
2011-08-03 15:50 ` Nicolas Pitre
2011-08-03 16:44 ` Stephen Boyd [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=4E397AF9.8070702@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@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 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.