__ro_after_init is no longer new and under development. Update the
document to reflect the correct status.
Signed-off-by: Shuah Khan <[email protected]>
---
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.
What remains are variables that are updated rarely (e.g. GDT). These
will need another infrastructure (similar to the temporary exceptions
--
2.32.0
Shuah Khan <[email protected]> writes:
> __ro_after_init is no longer new and under development. Update the
> document to reflect the correct status.
>
> Signed-off-by: Shuah Khan <[email protected]>
> ---
> 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