linux-kernel - Re: [PATCH v2 08/11] kbuild: create *.mod with full directory path and remove MODVERDIR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f1222c8a-9301-1e76-981d-a36e8687a29f@redhat.com>
Date:   Thu, 18 Jul 2019 16:18:33 -0400
From:   Joe Lawrence <joe.lawrence@...hat.com>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        Sam Ravnborg <sam@...nborg.org>,
        Nicolas Pitre <nico@...xnic.net>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Michal Marek <michal.lkml@...kovi.net>
Subject: Re: [PATCH v2 08/11] kbuild: create *.mod with full directory path
 and remove MODVERDIR

On 7/17/19 1:21 AM, Masahiro Yamada wrote:
>> Hi Masahiro,
>>
>> I'm following this patchset changes as they will affect the klp-convert
>> series [1] that the livepatching folks have been working on...
> 
> Empty files .tmp_versions/*.livepatch are touched
> to keep track of 'LIVEPATCH_* := y', right?
> 

Pretty much.  From that patchset I think the rework would need to  modify..

- [PATCH v4 02/10] kbuild: Support for Symbols.list creation: creates a 
Symbols.list file of kernel and module symbols, but *not* including any 
from LIVEPATCH_* modules.

- [PATCH v4 05/10] modpost: Integrate klp-convert: if a LIVEPATCH_* 
module has changed, call a newly introduced klp-convert script on it.

- [PATCH v4 06/10] modpost: Add modinfo flag to livepatch modules: find 
any LIVEPATCH_* mod, add it to a livepatchmods file, then pass that file 
to modpost

> Perhaps, adding a new field
> to *.mod files might be cleaner.

I can look into that.  By "field" you mean a new row in the file?

Regards,

-- Joe