Re: linux-next: build failure after merge of the xen-tip tree

["Jürgen Groß" <jgross@suse.com>]

[-- Attachment #1.1.1: Type: text/plain, Size: 1013 bytes --]

On 04.08.26 20:00, Val Packett wrote:
> 
> 
> El 4 de agosto de 2026 1:28:36 p. m. ART, Mark Brown <broonie@kernel.org> escribió:
>> Hi all,
>>
>> After merging the xen-tip tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> ERROR: modpost: "init_mm" [drivers/xen/xen-privcmd.ko] undefined!
>>
>> Caused by commit
>>
>>   64d26fb2ad1f2 (xen: privcmd: fix ioeventfd crash under PV domain)
>>
>> I have used the tree from next-20260803 instead.
> 
> Sorry for the trouble! Did not expect that to get applied so quickly.. I had noticed recently in my own testing that that patch wasn't actually ready to go in due to the symbol visibility issue, right. I'll work on resolving it.
> ~val

I'm pretty sure mm maintainers wouldn't like init_mm to be exported to
modules.

I'd go for a special variant of xen_remap_domain_mfn_array() mapping just
a single pfn into init_mm. This could be implemented in mmu_pv.c avoiding
the need to export init_mm.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]