[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50385948-5eb4-47ea-87f8-add4265933d6@redhat.com>
Date: Mon, 11 Dec 2023 13:03:27 +0100
From: David Hildenbrand <david@...hat.com>
To: Mark Brown <broonie@...nel.org>,
Suren Baghdasaryan <surenb@...gle.com>
Cc: akpm@...ux-foundation.org, viro@...iv.linux.org.uk,
brauner@...nel.org, shuah@...nel.org, aarcange@...hat.com,
lokeshgidra@...gle.com, peterx@...hat.com, ryan.roberts@....com,
hughd@...gle.com, mhocko@...e.com, axelrasmussen@...gle.com,
rppt@...nel.org, willy@...radead.org, Liam.Howlett@...cle.com,
jannh@...gle.com, zhangpeng362@...wei.com, bgeffon@...gle.com,
kaleshsingh@...gle.com, ngeoffray@...gle.com, jdduke@...gle.com,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [PATCH v6 5/5] selftests/mm: add UFFDIO_MOVE ioctl test
On 11.12.23 12:15, Mark Brown wrote:
> On Sun, Dec 10, 2023 at 07:04:19PM -0800, Suren Baghdasaryan wrote:
>> On Sun, Dec 10, 2023 at 5:01 PM Suren Baghdasaryan <surenb@...gle.com> wrote:
>
>>> Thanks for reporting! I'll try that later today.
>>> Just to clarify, are you using mm-unstable and if so, has it been
>>> rebased since Friday? There was an update to this patchset in
>>> mm-unstable which Andrew merged on Friday and the failure does look
>>> like something that would happen with the previous version.
>
>> I tried reproducing the issue but so far unsuccessfully. Could you
>> please confirm that on the latest mm-unstable branch it's still
>> reproducible and if so, please provide detailed instructions on how
>> you reproduce it.
>
> This is linux-next. I pasted the commands used to build and sent links
> to a full build log in the original report.
Probably also related to "make headers-install":
https://lkml.kernel.org/r/20231209020144.244759-1-jhubbard@nvidia.com
The general problem is that some mm selftests are currently not written
in way that allows them to compile with old linux headers. That's why
the build fails if "make headers-install" was not executed, but it does
not fail if "make headers-install" was once upon a time executed, but
the headers are outdated.
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists