linux-kernel - Re: optee: regression with kernel v5.14 (virtualization)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 28 Sep 2021 16:15:27 +0300
From:   Volodymyr Babchuk <vlad.babchuk@...il.com>
To:     Jerome Forissier <jerome@...issier.org>
Cc:     Jens Wiklander <jens.wiklander@...aro.org>,
        Sumit Garg <sumit.garg@...aro.org>,
        "op-tee@...ts.trustedfirmware.org" <op-tee@...ts.trustedfirmware.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Tyler Hicks <tyhicks@...ux.microsoft.com>
Subject: Re: optee: regression with kernel v5.14 (virtualization)

Hi Jerome,

On Tue, 28 Sept 2021 at 16:08, Jerome Forissier <jerome@...issier.org> wrote:
>
> Hi,
>
> I met an issue when testing OP-TEE with the latest released kernel
> (v5.14). The kernel won't boot when virtualization is enabled. More
> precisely, the boot hangs as the optee driver is probed. The last line
> on the console is:
>
> [xxx] optee: probing for conduit method.
>
> The issue can easily be reproduced in the QEMU OP-TEE environment as
> documented in [1]:
>
> $ repo init -u https://github.com/OP-TEE/manifest.git -m qemu_v8.xml
> $ repo sync -j10
> $ cd linux
> $ git fetch github --unshallow
> $ git checkout v5.14
> $ cd ../build
> $ make -j2 toolchains
> $ make -j10 XEN_BOOT=y run
>
> [Note, if you switch between XEN_BOOT=y and the default build, you need
> to "make arm-tf-clean"]
>
> git bisect points at commit b5c10dd04b74 ("optee: Clear stale cache
> entries during initialization") and reverting this commit on top of
> v5.14 does resolve the issue.
>
> Any idea what's wrong?

Yes, there was a small mistake in the mediator. My colleague already
pushed the patch. It is at staging now:

http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=1c3ed9c908732d19660fbe83580674d585464d4c

And will be backported to Xen 4.13+


-- 
WBR Volodymyr Babchuk aka lorc [+380976646013]
mailto: vlad.babchuk@...il.com