linux-kernel - Re: latent problem in free_init

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:	Fri, 19 Mar 2010 07:02:17 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Jan Beulich <JBeulich@...ell.com>
CC:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: latent problem in free_init_pages()

On 3/19/2010 3:25, Jan Beulich wrote:
> The calls to set_memory_rw() and set_memory_np() that both of you
> added for 2.6.25 imply that both "begin" and "end" are page aligned.
> This isn't the case, however, for the initrd and SMP locks. While at
> present this doesn't appear to do any harm, it partly subverts the
> debugging effect of the latter change and would result in a real issue
> if the .smp_locks section was moved into the read-only portion of the
> kernel image (where it really belongs imo).

if you change the linker script to move the section, you should also move it to
keep the end page aligned.

solving that at link time (like is done now) is obviously nicer than solving it at runtime ;-)
--
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/