mbox series

[0/1,jammy/kinetic,linux] Resolve synchronous exception on arm64

Message ID 20230608163727.585219-1-tim.gardner@canonical.com
Headers show
Series Resolve synchronous exception on arm64 | expand

Message

Tim Gardner June 8, 2023, 4:37 p.m. UTC 
BugLink: https://bugs.launchpad.net/bugs/2023311

SRU Justification

[Impact]

MSFT has requested the inclusion of commit e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64:
efi: Recover from synchronous exceptions occurring in firmware'). It looks generic enough to
apply to the master kernels.

Unlike x86, which has machinery to deal with page faults that occur during the execution of
EFI runtime services, arm64 has nothing like that, and a synchronous exception raised by
firmware code brings down the whole system.

[Test Plan]

This looks like a hard one to reproduce. Boot and regression testing should be sufficient.

[Regression Potential]

Firmware exceptions could still take down the system.

[Other Info]

SF: #00362062

Comments

Andrei Gherzan June 9, 2023, 1:39 p.m. UTC | #1 
On 23/06/08 10:37AM, Tim Gardner wrote:
> BugLink: https://bugs.launchpad.net/bugs/2023311
> 
> SRU Justification
> 
> [Impact]
> 
> MSFT has requested the inclusion of commit e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64:
> efi: Recover from synchronous exceptions occurring in firmware'). It looks generic enough to
> apply to the master kernels.
> 
> Unlike x86, which has machinery to deal with page faults that occur during the execution of
> EFI runtime services, arm64 has nothing like that, and a synchronous exception raised by
> firmware code brings down the whole system.
> 
> [Test Plan]
> 
> This looks like a hard one to reproduce. Boot and regression testing should be sufficient.
> 
> [Regression Potential]
> 
> Firmware exceptions could still take down the system.
> 
> [Other Info]
> 
> SF: #00362062

Acked-by: Andrei Gherzan <andrei.gherzan@canonical.com>
Philip Cox June 9, 2023, 3 p.m. UTC | #2 
On Thu, Jun 8, 2023 at 12:38 PM Tim Gardner <tim.gardner@canonical.com>
wrote:

> BugLink: https://bugs.launchpad.net/bugs/2023311
>
> SRU Justification
>
> [Impact]
>
> MSFT has requested the inclusion of commit
> e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64:
> efi: Recover from synchronous exceptions occurring in firmware'). It looks
> generic enough to
> apply to the master kernels.
>
> Unlike x86, which has machinery to deal with page faults that occur during
> the execution of
> EFI runtime services, arm64 has nothing like that, and a synchronous
> exception raised by
> firmware code brings down the whole system.
>
> [Test Plan]
>
> This looks like a hard one to reproduce. Boot and regression testing
> should be sufficient.
>
> [Regression Potential]
>
> Firmware exceptions could still take down the system.
>
> [Other Info]
>
> SF: #00362062
>
>
Stefan Bader June 15, 2023, 3:14 p.m. UTC | #3 
On 08.06.23 18:37, Tim Gardner wrote:
> BugLink: https://bugs.launchpad.net/bugs/2023311
> 
> SRU Justification
> 
> [Impact]
> 
> MSFT has requested the inclusion of commit e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64:
> efi: Recover from synchronous exceptions occurring in firmware'). It looks generic enough to
> apply to the master kernels.
> 
> Unlike x86, which has machinery to deal with page faults that occur during the execution of
> EFI runtime services, arm64 has nothing like that, and a synchronous exception raised by
> firmware code brings down the whole system.
> 
> [Test Plan]
> 
> This looks like a hard one to reproduce. Boot and regression testing should be sufficient.
> 
> [Regression Potential]
> 
> Firmware exceptions could still take down the system.
> 
> [Other Info]
> 
> SF: #00362062
> 
> 

Applied to kinetic,jammy:linux/master-next. Thanks.

-Stefan