On Fri, Sep 1, 2023 at 12:29 PM Hugh Dickins <hughd@xxxxxxxxxx> wrote:
>
>
> Thanks for all the info, which has helped in several ways. The only
> thing I can do is to offer you a debug (and then keep running) patch -
> suitable for the config you showed there, not for anyone else's config.
>
> I've never used stackdepot before, but I've tried this out in good and
> bad cases, and expect it to work for you, shedding light on where is
> going wrong - machine should boot up fine, and in dmesg you'll find one
> stacktrace between "WARNING: pte_map..." and "End of pte_map..." lines.
>
> To apply on top of a349d72fd9ef ("mm/pgtable: add rcu_read_lock() and
> rcu_read_unlock()s"), the bad end point of your bisection; but if you
> prefer, I can provide a version to go on top of whatever later Linus
> commit suits you.
>
> Patch not for general consumption, just for Mike's debugging:
> please report back the stacktrace shown - thanks!
>
Thanks for digging into the problem.
With the attached patch I got FTBFS when build kernel at commit a349d72fd9ef.
LD [M] drivers/gpu/drm/amd/amdgpu/amdgpu.o
MODPOST Module.symvers
ERROR: modpost: "pte_unmap" [arch/x86/kvm/kvm.ko] undefined!
ERROR: modpost: "pte_unmap" [drivers/vfio/vfio_iommu_type1.ko] undefined!
make[2]: *** [scripts/Makefile.modpost:144: Module.symvers] Error 1
make[1]: *** [/home/mikhail/packaging-work/git/linux/Makefile:1984:
modpost] Error 2
make: *** [Makefile:234: __sub-make] Error 2
--
Best Regards,
Mike Gavrilov.
<<attachment: build-log.zip>>
