linux-kernel - Re: oprofile BUG() in current kernel.

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: <1210676392.3939.4.camel@dao.KWGR614>
Date:	Tue, 13 May 2008 11:59:52 +0100
From:	Gianni Tedesco <gxt@...nott.ac.uk>
To:	Eric Dumazet <dada1@...mosbay.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	arges@...ux.vnet.ibm.com, Maynard Johnson <maynardj@...ibm.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	linux-kernel@...r.kernel.org, oprofile-list@...ts.sourceforge.net,
	Mike Travis <travis@....com>
Subject: Re: oprofile BUG() in current kernel.

On Tue, 2008-05-13 at 12:25 +0200, Eric Dumazet wrote:
> Gianni Tedesco a écrit :
> >
> >
> > Nope, exact same bad paging request in kernel mode... probably the bug
> > is something deep in oprofile then?
> >   
> Hum... Are you using oprofile as a module or statically included in kernel ?

Yes module

> Current module loader only allocates percpu room by examining 
> ".data.percpu" section and should be augmented to also look at 
> ".data.percpu.shared_aligned"
> Or, change DEFINE_PER_CPU_SHARED_ALIGNED() for modules (to use 
> ".data.percpu" only)
> 
> Anyway, with the per_cpu conversion of cpu_buffer, we dont need to 
> request cache_line alignment anymore
> 
> [PATCH] oprofile: Dont request cache line alignment for cpu_buffer

Nice theory, but with percpu + this patch, it still leads to the same
BUG trap :(

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