linux-kernel - Re: [PATCH] x86/kaslr: Fix typo in documentation

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]

Date:	Tue, 14 Apr 2015 13:37:33 +0200
From:	Borislav Petkov <bp@...e.de>
To:	Miroslav Benes <mbenes@...e.cz>
Cc:	corbet@....net, mingo@...hat.com, hpa@...or.com,
	tglx@...utronix.de, jkosina@...e.cz, x86@...nel.org,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] x86/kaslr: Fix typo in documentation

On Tue, Apr 14, 2015 at 01:35:24PM +0200, Miroslav Benes wrote:
> Documentation/x86/boot.txt labels the bit in boot_params.hdr.loadflags
> as ALSR_FLAG while it should be KASLR_FLAG.
> 
> Signed-off-by: Miroslav Benes <mbenes@...e.cz>
> ---
>  Documentation/x86/boot.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt
> index 88b8589..69e1397 100644
> --- a/Documentation/x86/boot.txt
> +++ b/Documentation/x86/boot.txt
> @@ -406,7 +406,7 @@ Protocol:	2.00+
>  	- If 0, the protected-mode code is loaded at 0x10000.
>  	- If 1, the protected-mode code is loaded at 0x100000.
>  
> -  Bit 1 (kernel internal): ALSR_FLAG
> +  Bit 1 (kernel internal): KASLR_FLAG
>  	- Used internally by the compressed kernel to communicate
>  	  KASLR status to kernel proper.
>  	  If 1, KASLR enabled.

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/