lkml.org 
[lkml]   [2023]   [Oct]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH 00/10] Handle set_memory_XXcrypted() errors
    From
    On 10/23/23 09:47, Michael Kelley (LINUX) wrote:
    > For paranoid CoCo VM users, using panic_on_warn=1 seems workable.
    > However, with current code and this patch series, it's possible have
    > set_memory_decrypted() return an error and have set_memory_encrypted()
    > fix things up as best it can without generating any warnings. It seems
    > like we need a WARN or some equivalent mechanism if either of these
    > fails, so that CoCo VMs can panic if they don't want to run with any
    > inconsistencies (again, assuming the host isn't malicious).

    Adding a warning to the fixup path in set_memory_encrypted() would be
    totally fine with me.

    \
     
     \ /
      Last update: 2023-10-23 18:58    [W:3.489 / U:0.204 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site