linux-kernel - Re: [crash] Re: Latest brk patchset

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]

Date:	Tue, 17 Mar 2009 12:59:38 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [crash] Re: Latest brk patchset

H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
>>
>> Here's an updated patch:
>>
>
> I already pushed an update (and you should have gotten notification 
> email)... 

Mail went to Citrix, which I don't check as regularly.

> can you verify that it matches what the end result should be in your 
> opinion?

Yep, looks good.

I've rebased the other two changes:

The following changes since commit 60ac98213914cc615c67e84bfb964aa95a080d13:
  H. Peter Anvin (1):
        x86-32: tighten the bound on additional memory to map

are available in the git repository at:

  ssh://master.kernel.org/~jeremy/git/xen.git tip/x86/setup-memory

Jeremy Fitzhardinge (2):
      x86/brk: make the brk reservation symbols inaccessible from C
      x86/brk: put the brk reservations in their own section

 arch/x86/include/asm/setup.h     |   10 +++++-----
 arch/x86/kernel/vmlinux_32.lds.S |    8 +++++---
 arch/x86/kernel/vmlinux_64.lds.S |    4 +++-
 3 files changed, 13 insertions(+), 9 deletions(-)


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