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:   Fri, 23 Dec 2016 13:54:50 +0100 (CET)
From:   Miroslav Benes <>
To:     Josh Poimboeuf <>
cc:     Jessica Yu <>, Jiri Kosina <>,
        Petr Mladek <>,,,
        Michael Ellerman <>,
        Heiko Carstens <>,,,,
        Vojtech Pavlik <>, Jiri Slaby <>,
        Chris J Arges <>,
        Andy Lutomirski <>,
        Ingo Molnar <>,
        Peter Zijlstra <>
Subject: Re: [PATCH v3 08/15] livepatch: separate enabled and patched

On Thu, 8 Dec 2016, Josh Poimboeuf wrote:

> Once we have a consistency model, patches and their objects will be
> enabled and disabled at different times.  For example, when a patch is
> disabled, its loaded objects' funcs can remain registered with ftrace
> indefinitely until the unpatching operation is complete and they're no
> longer in use.
> It's less confusing if we give them different names: patches can be
> enabled or disabled; objects (and their funcs) can be patched or
> unpatched:
> - Enabled means that a patch is logically enabled (but not necessarily
>   fully applied).
> - Patched means that an object's funcs are registered with ftrace and
>   added to the klp_ops func stack.
> Also, since these states are binary, represent them with booleans
> instead of ints.
> Signed-off-by: Josh Poimboeuf <>

Acked-by: Miroslav Benes <>


Powered by blists - more mailing lists