On Mon, Dec 11, 2023 at 8:25 AM Mark Brown broonie@kernel.org wrote:
On Mon, Dec 11, 2023 at 08:15:11AM -0800, Suren Baghdasaryan wrote:
On Mon, Dec 11, 2023 at 4:24 AM Mark Brown broonie@kernel.org wrote:
Oh, it's obviously the new headers not being installed. The builds where I'm seeing the problem (my own and KernelCI's) are all fresh containers so there shouldn't be any stale headers lying around.
Ok, I was updating my headers and that's why I could not reproduce it. David, should the test be modified to handle old linux headers (disable the new tests #ifndef _UFFDIO_MOVE or some other way)?
Are you sure we're not just missing an updated to the list of headers to copy (under include/uapi IIRC)?
Let me double check.
Just to rule out this possibility, linux-next was broken on Friday (see https://lore.kernel.org/all/CAJuCfpFiEqRO4qkFZbUCmGZy-n_ucqgR5NeyvnwXqYh+RU4...). I just checked and it's fixed now. Could you confirm that with the latest linux-next you still see the issue?