linux-kernel - Re: [PATCH v1.1] x86/mm/ASLR: Propagate ASLR status to kernel proper

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150402111915.GC3483@pd.tnic>
Date:	Thu, 2 Apr 2015 13:19:15 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Kees Cook <keescook@...omium.org>, x86-ml <x86@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v1.1] x86/mm/ASLR: Propagate ASLR status to kernel proper

On Thu, Apr 02, 2015 at 01:07:13PM +0200, Ingo Molnar wrote:
> So doesn't a 'nokaslr' boot option still make sense, to be able to 
> debug KASLR failures and such?

That's still parsed in arch/x86/boot/compressed/aslr.c

> > +	if (kaslr_enabled())
> > +		pr_emerg("Kernel Offset: 0x%lx from 0x%lx (relocation range: 0x%lx-0x%lx)\n",
> > +			 (unsigned long)&_text - __START_KERNEL,
> > +			 __START_KERNEL,
> > +			 __START_KERNEL_map,
> > +			 MODULES_VADDR-1);
> > +	else
> > +		pr_emerg("Kernel Offset: disabled\n");
> 
> Nit: curly braces for multi-line statements and so.

I guess by multi-line you mean multiple source lines...

-- 
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/