From: "Denys Dmytriyenko" <denis@denix.org>
To: Yann Dirson <yann.dirson@blade-group.com>
Cc: Ross Burton <ross@burtonini.com>,
meta-arm@lists.yoctoproject.org,
Yann Dirson <yann@blade-group.com>
Subject: Re: [meta-arm] [PATCH v2 3/6] arm/optee-os: deploy tee.elf for u-boot
Date: Tue, 20 Apr 2021 11:50:52 -0400 [thread overview]
Message-ID: <20210420155052.GL15937@denix.org> (raw)
In-Reply-To: <CA+4=imZLnifL-JUUMtFDJ8PbA3rNi0aF-tgC-MyMDAJ+fTKjWA@mail.gmail.com>
On Tue, Apr 20, 2021 at 11:35:55AM +0200, Yann Dirson wrote:
> *
>
> Le mar. 20 avr. 2021 à 09:54, Yann Dirson
> <yann.dirson@blade-group.com> a écrit :
> >
> > Le mar. 20 avr. 2021 à 02:18, Denys Dmytriyenko <denis@denix.org> a écrit :
> > >
> > > On Mon, Apr 19, 2021 at 05:34:13PM +0100, Ross Burton wrote:
> > > > This is causing the CI to break:
> > > >
> > > > ERROR: optee-os-3.11.0-r0 do_package_qa: QA Issue: optee-os: ELF
> > > > binary /lib/firmware/tee.elf has relocations in .text [textrel]
> > > >
> > > > Can you either fix or add an INSANE_SKIP with a comment?
> > >
> > > Ah, sorry, forgot to mention that textrel needs to be added to INSANE_SKIP now
> > > that tee.elf gets packaged.
> >
> > I'm surprised, how is it that this test is not triggered on all boxes
> > (ie. on the master CI but not on testing
> > or on my box) ? I'm all for submitting a fix but it's harder to be
> > correct why I cannot reproduce the problem :)
>
> Digging this I am surprised by how hard it is to force a package_qa rerun:
> - the package_qa_* functions text is not included, so even changing
> them does not
> cause them to re-run
> - WARN_QA and ERROR_QA are part of BB_HASHBASE_WHITELIST, so adjusting
> this does not cause a rerun either
>
> It would seem interesting to have all of this part of the package_qa
> siginfo, right ?
>
> I have the clear feeling the workflow to investigate the issue is
> really suboptimal
> ("bitbake -c clean && find sstate-cache -delete" between each run).
I usually do -c cleansstate and then force -c compile -f to invalidate sstate
for a package.
> As for the issue at hand: I can now trigger package_qa at will, and
> adding more traces
> in textrel test I can see it is really executed on tee.elf, but it
> just passes the test.
>
> "objdump -p" and "objdump -r" just show nothing, so indeed no TEXTREL.
>
> On what configuration does the CI get this ?
I wonder if tee.elf for your platform is different. Are you building for qemu
or a real machine? I saw this QA issue reported for TI platforms before.
> > > > Ross
> > > >
> > > > On Wed, 14 Apr 2021 at 14:48, Yann Dirson <yann.dirson@blade-group.com> wrote:
> > > > >
> > > > > From: Yann Dirson <yann@blade-group.com>
> > > > >
> > > > > Integration of OP-TEE in the u-boot image is done with `TEE=tee.elf`,
> > > > > so this build artifact must be exported.
> > > > >
> > > > > U-boot integration can now be done in a BSP layer with something like
> > > > > this in `u-boot_%.bbappend`:
> > > > >
> > > > > # OP-TEE, dependent on "optee" DISTRO_FEATURES
> > > > >
> > > > > OPTEE_OEMAKE ?= " TEE=${DEPLOY_DIR_IMAGE}/optee/tee.elf"
> > > > >
> > > > > EXTRA_OEMAKE_append = " ${PACKAGECONFIG_CONFARGS}"
> > > > > PACKAGECONFIG[optee] = "${OPTEE_OEMAKE},,optee-os"
> > > > > PACKAGECONFIG_append = " ${@bb.utils.filter('DISTRO_FEATURES', 'optee', d)}"
> > > > >
> > > > > Signed-off-by: Yann Dirson <yann@blade-group.com>
> > > > > ---
> > > > > meta-arm/recipes-security/optee/optee-os.inc | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/meta-arm/recipes-security/optee/optee-os.inc b/meta-arm/recipes-security/optee/optee-os.inc
> > > > > index 34f586a..08cc2f0 100644
> > > > > --- a/meta-arm/recipes-security/optee/optee-os.inc
> > > > > +++ b/meta-arm/recipes-security/optee/optee-os.inc
> > > > > @@ -45,7 +45,7 @@ do_compile[cleandirs] = "${B}"
> > > > > do_install() {
> > > > > #install core in firmware
> > > > > install -d ${D}${nonarch_base_libdir}/firmware/
> > > > > - install -m 644 ${B}/core/*.bin ${D}${nonarch_base_libdir}/firmware/
> > > > > + install -m 644 ${B}/core/*.bin ${B}/core/tee.elf ${D}${nonarch_base_libdir}/firmware/
> > > > >
> > > > > #install TA devkit
> > > > > install -d ${D}${includedir}/optee/export-user_ta/
> > > > > --
> > > > > 2.30.2
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> > > --
> > > Regards,
> > > Denys Dmytriyenko <denis@denix.org>
> > > PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
> > > Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
> >
> >
> >
> > --
> > Yann Dirson <yann@blade-group.com>
> > Blade / Shadow -- http://shadow.tech
>
>
>
> --
> Yann Dirson <yann@blade-group.com>
> Blade / Shadow -- http://shadow.tech
>
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
next prev parent reply other threads:[~2021-04-20 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 13:47 [PATCH v2 0/6] improving OP-TEE support for u-boot-based platforms Yann Dirson
2021-04-14 13:47 ` [PATCH v2 1/6] arm/optee: use pycryptodome rather pycryptodomex Yann Dirson
2021-04-14 13:47 ` [PATCH v2 2/6] arm/optee-os: mark LDFLAGS patch as submitted Yann Dirson
2021-04-14 13:47 ` [PATCH v2 3/6] arm/optee-os: deploy tee.elf for u-boot Yann Dirson
2021-04-19 16:34 ` [meta-arm] " Ross Burton
2021-04-20 0:17 ` Denys Dmytriyenko
2021-04-20 7:54 ` Yann Dirson
2021-04-20 9:35 ` Yann Dirson
2021-04-20 15:50 ` Denys Dmytriyenko [this message]
2021-04-20 17:06 ` Yann Dirson
2021-04-20 2:30 ` Jon Mason
2021-04-14 13:47 ` [PATCH v2 4/6] optee-client: use /var/lib/tee instead of /data/tee for persistent storage Yann Dirson
2021-04-14 13:47 ` [PATCH v2 5/6] optee-os: don't override upstream TA_LOG_LEVEL setting Yann Dirson
2021-04-14 13:47 ` [PATCH v2 6/6] RFC: optee-os: provide a "debug" PACKAGECONFIG flag Yann Dirson
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=20210420155052.GL15937@denix.org \
--to=denis@denix.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=ross@burtonini.com \
--cc=yann.dirson@blade-group.com \
--cc=yann@blade-group.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.