linux-kernel - Re: [patch] x86, bts: use atomic memory allocation

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: <1237575591.6387.2.camel@raistlin>
Date:	Fri, 20 Mar 2009 19:59:51 +0100
From:	Markus Metzger <markus.t.metzger@...glemail.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"Metzger, Markus T" <markus.t.metzger@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"hpa@...or.com" <hpa@...or.com>,
	"roland@...hat.com" <roland@...hat.com>,
	"eranian@...glemail.com" <eranian@...glemail.com>,
	"oleg@...hat.com" <oleg@...hat.com>,
	"Villacis, Juan" <juan.villacis@...el.com>,
	"ak@...ux.jf.intel.com" <ak@...ux.jf.intel.com>
Subject: Re: [patch] x86, bts: use atomic memory allocation

On Fri, 2009-03-20 at 19:55 +0100, Ingo Molnar wrote:
> * Metzger, Markus T <markus.t.metzger@...el.com> wrote:
> 

> > The second config boots OK with the additional changes to keep the 
> > GFP_KERNEL and move the ds_request_bts() calls out of the 
> > on_each_cpu() in the hw-branch-tracer.
> > 
> > I don't know yet what exactly causes the crash and if there is a 
> > simpler fix.
> 
> hm, this was an AMD box - so perhaps they dont have a compatible DS 
> implementation?

Hmmm, could be.

In that case, ds_cfg should be zero-initialized and ds_request should
return -EOPNOTSUPP. I'll try to simulate that.

regards,
markus.


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