[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a53a01b9-2907-4eb3-a9fd-16e6e8029028@citrix.com>
Date: Tue, 7 Apr 2020 18:23:27 +0100
From: Andrew Cooper <andrew.cooper3@...rix.com>
To: Peter Zijlstra <peterz@...radead.org>, <tglx@...utronix.de>,
<linux-kernel@...r.kernel.org>
CC: <hch@...radead.org>, <sean.j.christopherson@...el.com>,
<mingo@...hat.com>, <bp@...en8.de>, <hpa@...or.com>,
<x86@...nel.org>, <kenny@...ix.com>, <jeyu@...nel.org>,
<rasmus.villemoes@...vas.dk>, <pbonzini@...hat.com>,
<fenghua.yu@...el.com>, <xiaoyao.li@...el.com>,
<nadav.amit@...il.com>, <thellstrom@...are.com>,
<tony.luck@...el.com>, <rostedt@...dmis.org>,
<gregkh@...uxfoundation.org>, <jannh@...gle.com>,
<keescook@...omium.org>, <David.Laight@...lab.com>,
<dcovelli@...are.com>, <mhiramat@...nel.org>
Subject: Re: [PATCH 0/4] x86/module: Out-of-tree module decode and sanitize
On 07/04/2020 12:02, Peter Zijlstra wrote:
> Hi all,
>
> Driven by the SLD vs VMX interaction, here are some patches that provide means
> to analyze the text of out-of-tree modules.
>
> The first user of that is refusing to load modules on VMX-SLD conflicts, but it
> also has a second patch that refulses to load any module that tries to modify
> CRn/DRn.
>
> I'm thinking people will quickly come up with more and more elaborate tests to
> which to subject out-of-tree modules.
Anything playing with LGDT & friends? Shouldn't be substantially more
elaborate than CR/DR to check for.
~Andrew
Powered by blists - more mailing lists