From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Cc: "Su, Bao Cheng (RC-CN DF FA R&D)" <baocheng.su@siemens.com>,
"Lopes Ivo, Diogo Miguel (T CED IFD-PT)" <diogo.ivo@siemens.com>
Subject: Re: [PATCH] meta: optee-client: Generalize and update shutdown rule
Date: Thu, 12 Oct 2023 09:23:49 +0200 [thread overview]
Message-ID: <a5b7e833-0df0-4b1f-9e35-7e4fc65b2d4c@siemens.com> (raw)
In-Reply-To: <a9fa620684b618e6979f5c54d11b511800ad076b.camel@ilbers.de>
On 12.10.23 09:15, Uladzimir Bely wrote:
> On Thu, 2023-10-12 at 09:01 +0200, 'Jan Kiszka' via isar-users wrote:
>> On 11.10.23 16:36, 'Jan Kiszka' via isar-users wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> First, naming changed somewhere between kernel 5.10 and 6.1 so that
>>> optee-ta-bc50d971... is now optee-ta-supp-bc50d971...
>>>
>>> And then we should account for possibly more devices that need to
>>> be
>>> unbound. Use POSIX-compliant shell code for this.
>>>
>>> The generic loop allows to drop the explicit unmounting of efivarfs
>>> because the corresponding driver will already get unbound.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>> ---
>>> .../optee-client/files/debian/tee-supplicant.service | 3
>>> +--
>>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>>
>>> diff --git a/meta/recipes-bsp/optee-client/files/debian/tee-
>>> supplicant.service b/meta/recipes-bsp/optee-
>>> client/files/debian/tee-supplicant.service
>>> index cc92a5fd..d8b630a4 100644
>>> --- a/meta/recipes-bsp/optee-client/files/debian/tee-
>>> supplicant.service
>>> +++ b/meta/recipes-bsp/optee-client/files/debian/tee-
>>> supplicant.service
>>> @@ -13,8 +13,7 @@ Type=oneshot
>>> RemainAfterExit=yes
>>> # Start if not already started by the initramfs hook
>>> ExecStart=/bin/sh -c '/usr/bin/pgrep tee-supplicant >/dev/null ||
>>> /usr/sbin/tee-supplicant -d'
>>> -ExecStop=/bin/sh -c '/usr/bin/findmnt /sys/firmware/efi/efivars
>>>> /dev/null && /usr/bin/umount /sys/firmware/efi/efivars || true'
>>> -ExecStop=/bin/sh -c 'echo -n optee-ta-bc50d971-d4c9-42c4-82cb-
>>> 343fb7f37896 > /sys/bus/tee/drivers/optee-ftpm/unbind || true'
>>> +ExecStop=/bin/sh -c 'for dev in /sys/bus/tee/devices/*; do case
>>> "$dev" in *optee-ta-*) basename "$dev" > "$dev"/driver/unbind;;
>>> esac done'
>>> ExecStop=/usr/bin/pkill tee-supplicant
>>>
>>> [Install]
>>
>> Would be nice to get this quickly merged as well, then we could drop
>> all
>> isar patches again downstream.
>>
>
> The patch (as soon as another optee-client patch) are currently under
> CI testing (together with 3rd version of HOST_ARCH* patchset which now
> is OK with repro_test). If it passes OK (I expect by the end of the
> day) the patches will be merged.
>
> If there are some problems, I'll then check them separately.
>
Great, thanks!
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2023-10-12 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 14:36 Jan Kiszka
2023-10-12 7:01 ` Jan Kiszka
2023-10-12 7:15 ` Uladzimir Bely
2023-10-12 7:23 ` Jan Kiszka [this message]
2023-10-12 17:24 ` Uladzimir Bely
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=a5b7e833-0df0-4b1f-9e35-7e4fc65b2d4c@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=diogo.ivo@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.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