All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/testing: test_atf: bump the custom version to v2.5
Date: Sat, 28 Aug 2021 13:59:44 +0200	[thread overview]
Message-ID: <758e14a9-d79f-449a-dab0-1ec85a989458@mind.be> (raw)
In-Reply-To: <20210822194644.3260223-1-romain.naour@gmail.com>



On 22/08/2021 21:46, Romain Naour wrote:
> This version bump is needed to pass the ATF test with
> hardening option enabled (-fstack-protector-strong)
> 
> With the version v2.2, ATF fail due to undefined references:
> 
> ./build/juno/release/bl2u/arm_tzc400.o: In function `arm_tzc400_setup':
> arm_tzc400.c:(.text.arm_tzc400_setup+0x10): undefined reference to `__stack_chk_guard'
> arm_tzc400.c:(.text.arm_tzc400_setup+0x18): undefined reference to `__stack_chk_guard'
> arm_tzc400.c:(.text.arm_tzc400_setup+0xb8): undefined reference to `__stack_chk_guard'
> arm_tzc400.c:(.text.arm_tzc400_setup+0xcc): undefined reference to `__stack_chk_fail'
> 
> Signed-off-by: Romain Naour <romain.naour@gmail.com>

 I've added a reference to the build failure
(https://gitlab.com/buildroot.org/buildroot/-/jobs/1524842591), explained a bit
why it fails, and applied to master, thanks.


 Regards,
 Arnout

> ---
>  support/testing/tests/boot/test_atf.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/support/testing/tests/boot/test_atf.py b/support/testing/tests/boot/test_atf.py
> index a9d5b67ac7..4fcb9b241c 100644
> --- a/support/testing/tests/boot/test_atf.py
> +++ b/support/testing/tests/boot/test_atf.py
> @@ -10,7 +10,7 @@ class TestATFVexpress(infra.basetest.BRTest):
>          BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
>          BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
>          BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://github.com/ARM-software/arm-trusted-firmware.git"
> -        BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="v2.2"
> +        BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="v2.5"
>          BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="juno"
>          BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP=y
>          BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33=y
> 
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-08-28 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22 19:46 [Buildroot] [PATCH] support/testing: test_atf: bump the custom version to v2.5 Romain Naour
2021-08-24 22:02 ` Thomas Petazzoni
2021-08-25 11:12   ` Romain Naour
2021-08-28 11:59 ` Arnout Vandecappelle [this message]
2021-09-07 12:59 ` Peter Korsgaard

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=758e14a9-d79f-449a-dab0-1ec85a989458@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.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 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.