linux-kernel - Re: BUG: unable to handle kernel NULL pointer dereference at 00000002

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]

Message-ID: <20080729175043.GA11196@one.firstfloor.org>
Date:	Tue, 29 Jul 2008 19:50:43 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andi Kleen <andi@...stfloor.org>, Mike Galbraith <efault@....de>,
	Frederik Deweerdt <deweerdt@...e.fr>,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	suresh.b.siddha@...el.com, Ingo Molnar <mingo@...e.hu>,
	jblunck@...e.de
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000002

> That's not what datacenter people say. As long as power gain is bigger
> than performance loss.. they tend to want it.

That's a special case. It's fine but they should explicitely configure it.
I suspect even the data center people prefer "opt in" versus "opt out" here.

> Also "significantly" is extremely subjective, like in this case it can
> be a win or a loss, depending.

My impression is that the losses are more likely than the wins here.
> 
> > When the user says impacting performance
> > is ok then doing that is fine of course, but not by default.
> 
> that's a fine kernel policy.
> 
> Distros will override this policy if their users tell them they're
> willing to do the tradeoff.. they will pick that default. In fact..
> that's a big part of their job.. 

I'm not fully convinced that was done intentionally in this case.
If there's an explicit setting somewhere that's fine anyways, but I think
here it more looks like a mistake.

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