[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TYCPR01MB69938E7E2E14697FCF166155E5AD9@TYCPR01MB6993.jpnprd01.prod.outlook.com>
Date: Wed, 1 Mar 2023 03:12:08 +0000
From: "Tomohiro Misono (Fujitsu)" <misono.tomohiro@...itsu.com>
To: "'madvenka@...ux.microsoft.com'" <madvenka@...ux.microsoft.com>,
"jpoimboe@...hat.com" <jpoimboe@...hat.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"chenzhongjin@...wei.com" <chenzhongjin@...wei.com>,
"mark.rutland@....com" <mark.rutland@....com>,
"broonie@...nel.org" <broonie@...nel.org>,
"Keiya Nobuta (Fujitsu)" <nobuta.keiya@...itsu.com>,
"sjitindarsingh@...il.com" <sjitindarsingh@...il.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will@...nel.org" <will@...nel.org>,
"jamorris@...ux.microsoft.com" <jamorris@...ux.microsoft.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"live-patching@...r.kernel.org" <live-patching@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH v3 00/22] arm64: livepatch: Use ORC for dynamic frame
pointer validation
<snip>
> Testing
> =======
>
> - I have run all of the livepatch selftests successfully. I have written a
> couple of extra selftests myself which I will be posting separately
Hi,
What test configuration/environment you are using for test?
When I tried kselftest with fedora based config on VM, I got errors
because livepatch transition won't finish until signal is sent
(i.e. it takes 15s for every transition).
[excerpt from test result]
```
$ sudo ./test-livepatch.sh
TEST: basic function patching ... not ok
--- expected
+++ result
@@ -2,11 +2,13 @@
livepatch: enabling patch 'test_klp_livepatch'
livepatch: 'test_klp_livepatch': initializing patching transition
livepatch: 'test_klp_livepatch': starting patching transition
+livepatch: signaling remaining tasks
livepatch: 'test_klp_livepatch': completing patching transition
```
Thanks,
Tomohiro
>
> - I have a test driver to induce a NULL pointer exception to make sure
> that unwinding through exception handlers is reliable.
>
> - I use the test driver to create a timer to make sure that unwinding through
> the timer IRQ is reliable.
>
> - I call the unwinder from different places during boot to make sure that
> the unwinding in each of those cases is reliable.
>
Powered by blists - more mailing lists