linux-kernel - Re: 3.13: BUG: unable to handle kernel paging request at 00000000b4343e88

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: <52F27683.8090404@zytor.com>
Date:	Wed, 05 Feb 2014 09:36:03 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Peter Oberparleiter <oberpar@...ux.vnet.ibm.com>,
	Meelis Roos <mroos@...ux.ee>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 3.13: BUG: unable to handle kernel paging request at 00000000b4343e88

On 02/05/2014 09:00 AM, Peter Oberparleiter wrote:
> 
> Could you give this patch a try? It is a variation of the approach
> proposed in the discussion mentioned earlier and fixes the problem
> on my system.
> 

I would rather suggest that we explicitly disable gcov etc. from these
kinds of small, magic primitives.  Honestly, you're just trying to put a
bandaid on a gaping wound.

The real thing here is that hweight.c is not a normal C file, and we
shouldn't treat is as such.  It is a constrained environment, and trying
to tack crap like gcov to it is bound to lose, simply because gcov
doesn't know the rules it has to play by.

Even with the below change, if gcov clobbers, say, %rdx we're still screwed.

	-hpa

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