[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa51eb26-e2a9-c448-a3b8-e9e68deeb468@redhat.com>
Date: Wed, 22 Jul 2020 10:51:32 -0400
From: Joe Lawrence <joe.lawrence@...hat.com>
To: Kees Cook <keescook@...omium.org>, Miroslav Benes <mbenes@...e.cz>
Cc: Kristen Carlson Accardi <kristen@...ux.intel.com>, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, arjan@...ux.intel.com, x86@...nel.org,
linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com,
rick.p.edgecombe@...el.com, live-patching@...r.kernel.org
Subject: Re: [PATCH v4 00/10] Function Granular KASLR
On 7/22/20 10:39 AM, Kees Cook wrote:
> On Wed, Jul 22, 2020 at 11:27:30AM +0200, Miroslav Benes wrote:
>> Let me CC live-patching ML, because from a quick glance this is something
>> which could impact live patching code. At least it invalidates assumptions
>> which "sympos" is based on.
>
> In a quick skim, it looks like the symbol resolution is using
> kallsyms_on_each_symbol(), so I think this is safe? What's a good
> selftest for live-patching?
>
Hi Kees,
I don't think any of the in-tree tests currently exercise the
kallsyms/sympos end of livepatching.
I do have a local branch that does facilitate creating klp-relocations
that do rely upon this feature -- I'll try to see if I can get those
working with this patchset and report back later this week.
-- Joe
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
