From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master] optee: don't warn about missing OP-TEE header
Date: Thu, 29 Feb 2024 10:17:44 +0100 [thread overview]
Message-ID: <cd591f96-026f-4fc8-8f26-f572143b32e7@pengutronix.de> (raw)
In-Reply-To: <20240229091020.6fdnglwbla75hpn3@pengutronix.de>
On 29.02.24 10:10, Marco Felsch wrote:
> Hi Ahmad,
>
> On 24-02-28, Ahmad Fatoum wrote:
>> OP-TEE header is checked once in PBL, saved into scratch area after
>> verification and then checked again in barebox proper.
>>
>> The check in PBL fails silently, but the check in barebox proper that
>> should always follow, because the header isn't written to the scratch
>> area is printed with error log level.
>>
>> Printing an error in either case is wrong though as using a raw OP-TEE
>> binary without header is a valid use case and the OP-TEE header may
>> also be missing when barebox is chainloaded from a running barebox.
>>
>> Therefore reduce the message to debug log level.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>> common/optee.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/common/optee.c b/common/optee.c
>> index 34667f1f51e0..a8a43554e757 100644
>> --- a/common/optee.c
>> +++ b/common/optee.c
>> @@ -14,8 +14,8 @@ int optee_verify_header(const struct optee_header *hdr)
>> return -EINVAL;
>
> Shouldn't be the fix:
>
> if (IS_ERR_OR_NULL(hdr))
> return -EINVAL;
>
> to fail silently.
hdr is a valid pointer for me, but it doesn't point at a header, which causes
me to get an error message.
Thanks,
Ahmad
>
> Regards,
> Marco
>
>>
>> if (hdr->magic != OPTEE_MAGIC) {
>> - pr_err("Invalid header magic 0x%08x, expected 0x%08x\n",
>> - hdr->magic, OPTEE_MAGIC);
>> + pr_debug("Invalid header magic 0x%08x, expected 0x%08x\n",
>> + hdr->magic, OPTEE_MAGIC);
>> return -EINVAL;
>> }
>>
>> --
>> 2.39.2
>>
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-02-29 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 18:03 Ahmad Fatoum
2024-02-29 9:10 ` Marco Felsch
2024-02-29 9:17 ` Ahmad Fatoum [this message]
2024-02-29 9:33 ` Marco Felsch
2024-02-29 9:46 ` Ahmad Fatoum
2024-02-29 11:13 ` Marco Felsch
2024-02-29 11:46 ` Ahmad Fatoum
2024-03-01 9:21 ` Sascha Hauer
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=cd591f96-026f-4fc8-8f26-f572143b32e7@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.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