linux-kernel - Re: [PATCH] Documentation: DocBook: kgdb: update CONFIG_STRICT_KERNEL

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: <20170420150914.18399eb8@lwn.net>
Date:   Thu, 20 Apr 2017 15:09:14 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Li Qiang <liq3ea@...il.com>
Cc:     jason.wessel@...driver.com, labbott@...hat.com,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        kgdb-bugreport@...ts.sourceforge.net, Li Qiang <liqiang6-s@....cn>
Subject: Re: [PATCH] Documentation: DocBook: kgdb: update
 CONFIG_STRICT_KERNEL_RWX info

On Tue, 18 Apr 2017 18:58:45 -0700
Li Qiang <liq3ea@...il.com> wrote:

> CONFIG_STRICT_KERNEL_RWX is no longer selectable on most architectures.
> Update this info to the documentation.
> 
> Signed-off-by: Li Qiang <liqiang6-s@....cn>
> ---
>  Documentation/DocBook/kgdb.tmpl | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl
> index 856ac20..ef0b67b 100644
> --- a/Documentation/DocBook/kgdb.tmpl
> +++ b/Documentation/DocBook/kgdb.tmpl
> @@ -121,7 +121,9 @@
>      If kgdb supports it for the architecture you are using, you can
>      use hardware breakpoints if you desire to run with the
>      CONFIG_STRICT_KERNEL_RWX option turned on, else you need to turn off
> -    this option.
> +    this option. In most architectures, this option is not selectable.
> +    For this situation, it can be turned off by adding a runtime parameter
> +    'rodata=off'.

So this is an improvement, I guess, though the paragraph remains kind of
confusing.  Is there any chance we could actually just say which
architectures can use hardware breakpoints, and which should boot with
rodata=off?

Thanks,

jon