From: rusty@rustcorp.com.au (Rusty Russell) Date: Fri, 01 Nov 2013 12:58:29 +1030 Subject: [RFC PATCH] kernel/kallsyms.c: only show legal kernel symbol In-Reply-To: References: <20131024084559.GD16735@n2100.arm.linux.org.uk> <87mwlyclng.fsf@rustcorp.com.au> <87y55h7vcd.fsf@rustcorp.com.au> <87sivp7eai.fsf@rustcorp.com.au> <874n82gk89.fsf@rustcorp.com.au> <20131028132348.62f7e368@tom-ThinkPad-T410> <87ob6aeyg4.fsf@rustcorp.com.au> <20131030230920.GQ16735@n2100.arm.linux.org.uk> <87zjpqb08q.fsf@rustcorp.com.au> Message-ID: <87fvrgc0tu.fsf@rustcorp.com.au> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Ming Lei writes: > On Thu, Oct 31, 2013 at 11:14 AM, Rusty Russell wrote: >> Russell King - ARM Linux writes: >> >> Kallsyms tends to fall between modules and scripts. I assume it's not >> urgent, so no cc:stable on this one. > > Rusty, thanks a lot. > > BTW, there is already other report on the problem: > > http://lkml.indiana.edu/hypermail/linux/kernel/1310.3/02772.html OK, *that* references the commit which is the problem, when went into v3.11 (b9b32bf70f2fb710b07c94e13afbc729afe221da) Unfortunately, *that commit* was cc:stable, so this needs to be cc:stable as well, not just >= 3.11. Looking back on those patches, there's a mass of cc:stable on them. The descriptions are either misleading, or these patches prevent theoretical attacks which means they shouldn't have been cc:stable. Grr... Rusty.