linux-kernel - Re: kernel BUG at kernel/kallsyms.c:222!

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]

Date:	Mon, 11 Nov 2013 19:32:36 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Jonathan Austin <jonathan.austin@....com>
Cc:	Ming Lei <tom.leiming@...il.com>, Michal Marek <mmarek@...e.cz>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>, Axel Lin <axel.lin@...ics.com>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: kernel BUG at kernel/kallsyms.c:222!

On Mon, Nov 11, 2013 at 05:15:29PM +0000, Jonathan Austin wrote:
> I've tested the patch below and it solves the ARM side of things - so
> gives you an option other than a complete revert. Happy to put this in to
> RMK's patch system if you'd prefer not to have to revert and he's happy
> with the patch.

I think this is the right solution because it then means that this symbol
has the same meaning whether on MMU or !MMU - and getting rid of these
kinds of gratuitous variances are the only way that !MMU is going to
become less fragile.
--
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/