linux-kernel - 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]

Message-ID: <49BC4CAC.202@goop.org>
Date:	Sat, 14 Mar 2009 17:32:44 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Yinghai Lu <yinghai@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Latest brk patchset

H. Peter Anvin wrote:
> Hi guys,
>
> I was reviewing the latest brk patchset, and I have a question:
>
> Why is the brk merged into the .bss, instead of being left in its own
> (nobits) segment:
>
>   .bss : AT(ADDR(.bss) - LOAD_OFFSET) {
> 	__init_end = .;
> 	__bss_start = .;		/* BSS */
> 	*(.bss.page_aligned)
> 	*(.bss)
> 	. = ALIGN(4);
> 	__bss_stop = .;
>
> 	. = ALIGN(PAGE_SIZE);
> 	__brk_base = . ;
> 	. += 64 * 1024 ;	/* 64k slop space */
> 	*(.brk_reservation)	/* areas brk users have reserved */
> 	__brk_limit = . ;
>
>   	_end = . ;
>   }
>
> It really doesn't make much sense to me, and is more than a bit
> confusing given the symbols.
>   

Mostly because I knew that the bss would get mapped into the appropriate 
phdr segment correctly, but I wasn't sure that another bss-like section 
would be.  Also because historically the brk segment was just an 
extension of the executable's bss, and its more or less the same too.

Is there any real benefit in putting it into another section?

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