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] [day] [month] [year] [list]
Message-ID: <87r1akqilh.fsf@meer.lwn.net>
Date:   Fri, 10 Dec 2021 14:02:18 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Shuah Khan <skhan@...uxfoundation.org>
Cc:     Shuah Khan <skhan@...uxfoundation.org>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: update self-protection __ro_after_init status

Shuah Khan <skhan@...uxfoundation.org> writes:

> __ro_after_init is no longer new and under development. Update the
> document to reflect the correct status.
>
> Signed-off-by: Shuah Khan <skhan@...uxfoundation.org>
> ---
>  Documentation/security/self-protection.rst | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/security/self-protection.rst b/Documentation/security/self-protection.rst
> index f584fb74b4ff..910668e665cb 100644
> --- a/Documentation/security/self-protection.rst
> +++ b/Documentation/security/self-protection.rst
> @@ -81,8 +81,7 @@ of the kernel, gaining the protection of the kernel's strict memory
>  permissions as described above.
>  
>  For variables that are initialized once at ``__init`` time, these can
> -be marked with the (new and under development) ``__ro_after_init``
> -attribute.
> +be marked with the ``__ro_after_init`` attribute.
>  
Applied, thanks.

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ