linux-kernel - Re: Are Section mismatches out of control?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 2 Feb 2008 05:12:11 +0100
From:	Andi Kleen <ak@...e.de>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Andi Kleen <ak@...e.de>, Sam Ravnborg <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux arch <linux-arch@...r.kernel.org>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Are Section mismatches out of control?

On Fri, Feb 01, 2008 at 10:51:14PM +0100, Jan Engelhardt wrote:
> 
> On Feb 1 2008 12:10, Andi Kleen wrote:
> >On Friday 01 February 2008 11:47:18 Sam Ravnborg wrote:
> >> James said in a related posting that the Section mismatch
> >> warnings were getting out of control.
> >
> >My question is: where are crashes? If the sections were
> >really in such bad shape and since we poison (and sometimes
> >even unmap) init after boot we should in theory see a lot 
> >of oops reports from this if there were really accesses to
> >them after boot.
> >
> >Where are they?
> 
> Perhaps still in RAM? Explicitly zero the area after unmapping,
> maybe something happens.

This is already doing (but not with zero). With DEBUG_RODATA it is 
even unmapped. 

-Andi

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