linux-kernel - Re: [Build fail] i386 & nvdimm is unhappy

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: <d066788b-0f69-37e5-fd5c-12755f498677@infradead.org>
Date:   Thu, 29 Oct 2020 16:13:16 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Philip Li <philip.li@...el.com>,
        Dan Williams <dan.j.williams@...el.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>,
        kbuild test robot <lkp@...el.com>
Subject: Re: [Build fail] i386 & nvdimm is unhappy

On 10/29/20 4:09 PM, Philip Li wrote:
> On Thu, Oct 29, 2020 at 03:52:42PM -0700, Dan Williams wrote:
>> On Thu, Oct 29, 2020 at 3:44 PM Thomas Gleixner <tglx@...utronix.de> wrote:
>>>
>>> Dan,
>>>
>>> x86 32bit build fails with the config below with this:
>>>
>>>   ERROR: modpost: "phys_to_target_node" [drivers/nvdimm/nd_e820.ko]
>>>   undefined!
>>
>> Acknowledged, I'm on it.
>>
>> Wonder how 0-day missed this or I missed the 0-day report?
> Sorry about this Dan. Can you share some info like which kconfig and bad commit?
> We will investigate this to provide update in earliest time.
> 
> Thanks
> 
>>

I posted earlier today about the same failure on x86_64 & linux-next:

https://lore.kernel.org/linux-next/0faac4da-a7bc-3fc7-e278-ad4f72499224@infradead.org/T/#u


Thomas and I both included kernel config files.

-- 
~Randy