public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Joshua Watt <jpewhacker@gmail.com>, u-boot@lists.denx.de
Cc: Joshua Watt <JPEWhacker@gmail.com>,
	Igor Opaniuk <igor.opaniuk@gmail.com>,
	Sam Protsenko <semen.protsenko@linaro.org>,
	Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] android_ab: Fix backup offset calculation
Date: Fri, 16 Aug 2024 10:23:27 +0200	[thread overview]
Message-ID: <87zfpclvuo.fsf@baylibre.com> (raw)
In-Reply-To: <20240807141434.733085-1-JPEWhacker@gmail.com>

Hi Joshua,

Thank you for the patch.

On mer., août 07, 2024 at 08:13, Joshua Watt <jpewhacker@gmail.com> wrote:

> The backup offset is in bytes, but was incorrectly be interpreted as
> blocks, leading to it being written to the wrong location. Fix the
> calculation and clarify that ANDROID_AB_BACKUP_OFFSET is in bytes and
> must be a multiple of the block size.

Nice finding !

>
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> ---
>  boot/android_ab.c | 4 ++--
>  common/Kconfig    | 3 ++-
>  2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/boot/android_ab.c b/boot/android_ab.c
> index 143f373aae..b253200161 100644
> --- a/boot/android_ab.c
> +++ b/boot/android_ab.c
> @@ -139,8 +139,8 @@ static int ab_control_store(struct blk_desc *dev_desc,
>  {
>  	ulong abc_offset, abc_blocks, ret;
>  

Can we add a safeguard in here to make sure that offset
is always blksz aligned ?

We could do something similar to ab_control_create_from_disk():

	if (offset % part_info->blksz) {
		log_err("ANDROID: offset not block aligned.\n");
		return -EINVAL;
	}

> -	abc_offset = offset +
> -		     offsetof(struct bootloader_message_ab, slot_suffix) /
> +	abc_offset = (offset +
> +		      offsetof(struct bootloader_message_ab, slot_suffix)) /
>  		     part_info->blksz;
>  	abc_blocks = DIV_ROUND_UP(sizeof(struct bootloader_control),
>  				  part_info->blksz);

I've also noticed that ab_control_store()'s documentation does not
document the @param[in] offset.

Could we add that as well (either in a seperate patch or in this one) ?

> diff --git a/common/Kconfig b/common/Kconfig
> index 83c81edac2..e1b8557e0c 100644
> --- a/common/Kconfig
> +++ b/common/Kconfig
> @@ -986,7 +986,8 @@ config ANDROID_AB_BACKUP_OFFSET
>  	help
>  	  If non-zero, a backup bootloader message starting at this offset in
>  	  the partition will tried in the event that the primary one (starting
> -	  at offset 0) fails its checksum.
> +	  at offset 0) fails its checksum. The offset is in bytes and must be
> +	  multiple of the block size.
>  
>  endmenu
>  
> -- 
> 2.45.2

  reply	other threads:[~2024-08-16  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 14:13 [PATCH] android_ab: Fix backup offset calculation Joshua Watt
2024-08-16  8:23 ` Mattijs Korpershoek [this message]
2024-08-28  0:38 ` Sam Protsenko
2024-08-28 14:37 ` [PATCH v2] android_ab: Fixes: " Joshua Watt
2024-08-29  8:56   ` Mattijs Korpershoek
2024-09-05  6:56   ` Mattijs Korpershoek

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=87zfpclvuo.fsf@baylibre.com \
    --to=mkorpershoek@baylibre.com \
    --cc=igor.opaniuk@gmail.com \
    --cc=jpewhacker@gmail.com \
    --cc=semen.protsenko@linaro.org \
    --cc=trini@konsulko.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox