[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b97853f0-c4be-7039-1d4c-96b3ab802472@infradead.org>
Date: Wed, 24 Jun 2020 14:29:37 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Kees Cook <keescook@...omium.org>,
Richard Weinberger <richard@....at>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Prasad Sodagudi <psodagud@...eaurora.org>,
Sami Tolvanen <samitolvanen@...gle.com>,
Amit Daniel Kachhap <amit.kachhap@....com>,
linux-kselftest@...r.kernel.org,
clang-built-linux@...glegroups.com,
linux-kernel <linux-kernel@...r.kernel.org>,
Richard Weinberger <richard.weinberger@...il.com>
Subject: Re: [PATCH drivers/misc 0/4] lkdtm: Various clean ups
On 6/24/20 1:36 PM, Kees Cook wrote:
> On Wed, Jun 24, 2020 at 09:23:25AM +0200, Richard Weinberger wrote:
>> ----- Ursprüngliche Mail -----
>>>>> Regardless, it seems arch/x86/um/asm/desc.h is not needed any more?
>>>
>>>> True that, we can rip the file.
>>>
>>> Has anyone fixed the uml build errors?
>>
>> I didn't realize that this is a super urgent issue. ;-)
>>
>> Kees, if you want you can carry a patch in your series, I'll ack it.
>> Otherwise I can also do a patch and bring it via the uml tree upstream
>> as soon more fixes queued up.
>
> I think the lkdtm change will tweak this bug, so I'm happy to carry the
> patch (I just haven't had time to create and test one). Is it really
> just as simple as removing arch/x86/um/asm/desc.h?
>
I just tried that and the build is still failing, so No, it's not that simple.
But thanks for offering.
I'll just ignore the UML build errors for now.
--
~Randy
Powered by blists - more mailing lists