From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Igor Opaniuk <igor.opaniuk@gmail.com>, u-boot@lists.denx.de
Cc: Mattijs Korpershoek <mkorpershoek@kernel.org>,
Tom Rini <trini@konsulko.com>,
Igor Opaniuk <igor.opaniuk@gmail.com>
Subject: Re: [PATCH 1/2] libavb: update to AOSP 1.3.0
Date: Fri, 24 Jul 2026 14:34:53 +0200 [thread overview]
Message-ID: <87wluk7ehe.fsf@kernel.org> (raw)
In-Reply-To: <20260712-avb-libavb-1-3-v1-1-44a50dfe2f23@gmail.com>
Hi Igor,
Thank you for the patch.
On Sun, Jul 12, 2026 at 16:07, Igor Opaniuk <igor.opaniuk@gmail.com> wrote:
> Re-sync the vendored libavb from AOSP external/avb, moving from the ~2019
> snapshot (v1.1.0) to v1.3.0. v1.1.0 rejected any vbmeta whose required
> libavb minor version was greater than 1 with UNSUPPORTED_VERSION; this
> lifts that ceiling and picks up the accumulated upstream fixes.
>
> Synced from commit a1fe228b8654 ("libavb: support chain partition no ab"),
> which is where AVB version 1.3.0 was introduced (the vendored files match
> this commit exactly), for more details check [1].
>
> Functionality now parsed by the library:
> - AvbVBMetaImageHeader.rollback_index_location (v1.2)
> - AvbChainPartitionDescriptor flags / DO_NOT_USE_AB (v1.3)
> - AvbHashtreeDescriptor FLAGS_CHECK_AT_MOST_ONCE
> - AVB_HASHTREE_ERROR_MODE_PANIC
>
> The AvbOps callback set is unchanged, so the integration layer in
> common/avb_verify.c needs no changes.
>
> U-Boot-specific adaptations are preserved rather than pulling upstream's
> BoringSSL-oriented crypto restructure (sha/, boringssl/): the U-Boot port
> in avb_sysdeps.h / avb_sysdeps_posix.c and the flat avb_sha.h /
> avb_sha256.c / avb_sha512.c are kept as-is. The SHA API signatures are
> unchanged, so the retained implementation is compatible with the updated
> code.
>
> Imported files keep U-Boot's SPDX-License-Identifier header style
> and their upstream per-file licenses (avb_rsa.c stays MIT OR
> BSD-3-Clause). The unused, Apache-2.0-licensed avb_crc32.c is not
> imported.
>
> [1] https://android.googlesource.com/platform/external/avb/+/a1fe228b86543a21739c51352f5ce72f134fccfa
> Signed-off-by: Igor Opaniuk <igor.opaniuk@gmail.com>
I've reviewed this by comparing all the files with the reference
implementation from AOSP's external/avb.
This looks good to me, thanks!
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
next prev parent reply other threads:[~2026-07-24 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 14:07 [PATCH 0/2] libavb: update to AOSP 1.3.0 Igor Opaniuk
2026-07-12 14:07 ` [PATCH 1/2] " Igor Opaniuk
2026-07-24 12:34 ` Mattijs Korpershoek [this message]
2026-07-12 14:07 ` [PATCH 2/2] doc: android: refresh AVB provenance and pin libavb reference Igor Opaniuk
2026-07-24 12:35 ` Mattijs Korpershoek
2026-07-15 16:28 ` [PATCH 0/2] libavb: update to AOSP 1.3.0 Igor Opaniuk
2026-07-24 13:14 ` Mattijs Korpershoek
2026-07-27 7:38 ` Mattijs Korpershoek
2026-07-27 9:31 ` Igor Opaniuk
2026-07-27 12:30 ` 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=87wluk7ehe.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=igor.opaniuk@gmail.com \
--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