All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] common: env_nand: Ensure that we have nand_info[0] prior to use
Date: Mon, 15 Aug 2016 11:48:31 -0500	[thread overview]
Message-ID: <1471279711.25630.270.camel@buserror.net> (raw)
In-Reply-To: <1471276604-25544-1-git-send-email-trini@konsulko.com>

On Mon, 2016-08-15 at 11:56 -0400, Tom Rini wrote:
> Now that nand_info[] is an array of pointers we need to ensure that it's
> been populated prior to use.??We may for example have ENV in NAND set in
> configurations that run on boards with and without NAND (where default
> env is fine enough, such as omap3_beagle and beagleboard (NAND) vs
> beagle xM (no NAND)).
> 
> Fixes: b616d9b0a708 ("nand: Embed mtd_info in struct nand_chip")
> Cc: Scott Wood <oss@buserror.net>
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
> Changes in v2:
> - Oops, move check on the saveenv side in to erase_and_write_env
> ---
> ?common/env_nand.c | 9 +++++++--
> ?1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/common/env_nand.c b/common/env_nand.c
> index fc99a5e3fc0d..96a1020b5e79 100644
> --- a/common/env_nand.c
> +++ b/common/env_nand.c
> @@ -163,6 +163,9 @@ static int erase_and_write_env(const struct env_location
> *location,
> ?{
> ?	int ret = 0;
> ?
> +	if (!nand_info[0])
> +		return 1;
> +
> ?	printf("Erasing %s...\n", location->name);
> ?	if (nand_erase_opts(nand_info[0], &location->erase_opts))
> ?		return 1;
> @@ -244,10 +247,12 @@ static int readenv(size_t offset, u_char *buf)
> ?{
> ?	size_t end = offset + CONFIG_ENV_RANGE;
> ?	size_t amount_loaded = 0;
> -	size_t blocksize, len;
> +	size_t blocksize = 0, len;
> ?	u_char *char_ptr;
> ?
> -	blocksize = nand_info[0]->erasesize;
> +	if (nand_info[0])
> +		blocksize = nand_info[0]->erasesize;
> +
> ?	if (!blocksize)
> ?		return 1;
> ?

Messing around with blocksize rather than directly returning is awkward -- it
makes it look as if you could proceed with blocksize zero until you read the
next statement. ?And is there ever a case where blocksize can be zero, now
that uninitialized NAND devices will simply have a NULL pointer?

-Scott

  reply	other threads:[~2016-08-15 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 15:56 [U-Boot] [PATCH v2] common: env_nand: Ensure that we have nand_info[0] prior to use Tom Rini
2016-08-15 16:48 ` Scott Wood [this message]
2016-08-15 16:54   ` Tom Rini

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=1471279711.25630.270.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=u-boot@lists.denx.de \
    /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.