From: rusty@rustcorp.com.au (Rusty Russell)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] kernel/kallsyms.c: only show legal kernel symbol
Date: Fri, 01 Nov 2013 12:58:29 +1030 [thread overview]
Message-ID: <87fvrgc0tu.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CACVXFVMp-NWEVEG4-de2QHjUtwHUj+gWXOBjtUZge6_ZrT0UsA@mail.gmail.com>
Ming Lei <tom.leiming@gmail.com> writes:
> On Thu, Oct 31, 2013 at 11:14 AM, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Russell King - ARM Linux <linux@arm.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.
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chen Gang <gang.chen@asianux.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Michal Marek <mmarek@suse.cz>
Subject: Re: [RFC PATCH] kernel/kallsyms.c: only show legal kernel symbol
Date: Fri, 01 Nov 2013 12:58:29 +1030 [thread overview]
Message-ID: <87fvrgc0tu.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CACVXFVMp-NWEVEG4-de2QHjUtwHUj+gWXOBjtUZge6_ZrT0UsA@mail.gmail.com>
Ming Lei <tom.leiming@gmail.com> writes:
> On Thu, Oct 31, 2013 at 11:14 AM, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Russell King - ARM Linux <linux@arm.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.
next prev parent reply other threads:[~2013-11-01 2:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 3:18 [RFC PATCH] kernel/kallsyms.c: only show legal kernel symbol Ming Lei
2013-10-23 3:18 ` Ming Lei
2013-10-24 1:21 ` Rusty Russell
2013-10-24 1:21 ` Rusty Russell
2013-10-24 5:42 ` Ming Lei
2013-10-24 5:42 ` Ming Lei
2013-10-24 8:45 ` Russell King - ARM Linux
2013-10-24 8:45 ` Russell King - ARM Linux
2013-10-24 9:10 ` Ming Lei
2013-10-24 9:10 ` Ming Lei
2013-10-24 23:08 ` Rusty Russell
2013-10-24 23:08 ` Rusty Russell
2013-10-25 1:29 ` Ming Lei
2013-10-25 1:29 ` Ming Lei
2013-10-25 5:50 ` Rusty Russell
2013-10-25 5:50 ` Rusty Russell
2013-10-25 7:01 ` Ming Lei
2013-10-25 7:01 ` Ming Lei
2013-10-25 11:58 ` Rusty Russell
2013-10-25 11:58 ` Rusty Russell
2013-10-26 12:31 ` Ming Lei
2013-10-26 12:31 ` Ming Lei
2013-10-28 3:14 ` Rusty Russell
2013-10-28 3:14 ` Rusty Russell
2013-10-28 5:23 ` Ming Lei
2013-10-28 5:23 ` Ming Lei
2013-10-28 5:50 ` Rusty Russell
2013-10-28 5:50 ` Rusty Russell
2013-10-30 23:09 ` Russell King - ARM Linux
2013-10-30 23:09 ` Russell King - ARM Linux
2013-10-31 3:14 ` Rusty Russell
2013-10-31 3:14 ` Rusty Russell
2013-10-31 4:55 ` Ming Lei
2013-10-31 4:55 ` Ming Lei
2013-11-01 2:28 ` Rusty Russell [this message]
2013-11-01 2:28 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvrgc0tu.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.