[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87fvrgc0tu.fsf@rustcorp.com.au>
Date: Fri, 01 Nov 2013 12:58:29 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: Ming Lei <tom.leiming@...il.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Chen Gang <gang.chen@...anux.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Michal Marek <mmarek@...e.cz>
Subject: Re: [RFC PATCH] kernel/kallsyms.c: only show legal kernel symbol
Ming Lei <tom.leiming@...il.com> writes:
> On Thu, Oct 31, 2013 at 11:14 AM, Rusty Russell <rusty@...tcorp.com.au> wrote:
>> Russell King - ARM Linux <linux@....linux.org.uk> 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.
--
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/
Powered by blists - more mailing lists