[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54F1BA64.3020000@linux.intel.com>
Date: Sat, 28 Feb 2015 04:53:56 -0800
From: Arjan van de Ven <arjan@...ux.intel.com>
To: jesse.brandeburg@...el.com, mingo@...nel.org,
linux-kernel@...r.kernel.org, ast@...mgrid.com,
daniel@...earbox.net, bruce.w.allan@...el.com, hpa@...or.com,
tglx@...utronix.de, bp@...e.de, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/mm] x86/mm: Unexport set_memory_ro() and set_memory_rw()
On 2/28/2015 2:00 AM, tip-bot for Daniel Borkmann wrote:
> Commit-ID: 6bbb614ec478961c7443086bdf7fd6784479c14a
> Gitweb: http://git.kernel.org/tip/6bbb614ec478961c7443086bdf7fd6784479c14a
> Author: Daniel Borkmann <daniel@...earbox.net>
> AuthorDate: Fri, 27 Feb 2015 15:55:40 +0100
> Committer: Ingo Molnar <mingo@...nel.org>
> CommitDate: Sat, 28 Feb 2015 10:41:59 +0100
>
> x86/mm: Unexport set_memory_ro() and set_memory_rw()
>
> This effectively unexports set_memory_ro() and set_memory_rw()
> functions, and thus reverts:
>
> a03352d2c1dc ("x86: export set_memory_ro and set_memory_rw").
>
> They have been introduced for debugging purposes in e1000e, but
> no module user is in mainline kernel (anymore?) and we
> explicitly do not want modules to use these functions, as they
> i.e. protect eBPF (interpreted & JIT'ed) images from malicious
> modifications or bugs.
>
> Outside of eBPF scope, I believe also other set_memory_*()
> functions should be unexported on x86 for modules.
>
Acked-by: Arjan van de Ven <arjan@...ux.intel.com>
--
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