linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Ryan Roberts <ryan.roberts@arm.com>,
	Suren Baghdasaryan <surenb@google.com>,
	akpm@linux-foundation.org
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, shuah@kernel.org,
	aarcange@redhat.com, lokeshgidra@google.com, peterx@redhat.com,
	hughd@google.com, mhocko@suse.com, axelrasmussen@google.com,
	rppt@kernel.org, willy@infradead.org, Liam.Howlett@oracle.com,
	jannh@google.com, zhangpeng362@huawei.com, bgeffon@google.com,
	kaleshsingh@google.com, ngeoffray@google.com, jdduke@google.com,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	kernel-team@android.com
Subject: Re: [PATCH v5 5/5] selftests/mm: add UFFDIO_MOVE ioctl test
Date: Fri, 1 Dec 2023 21:47:07 +0100	[thread overview]
Message-ID: <a41c759f-78d8-44ed-b708-1bb737a8e6c1@redhat.com> (raw)
In-Reply-To: <b3c882d2-0135-430c-8179-784f78be0902@arm.com>

On 01.12.23 10:29, Ryan Roberts wrote:
> On 21/11/2023 17:16, Suren Baghdasaryan wrote:
>> Add tests for new UFFDIO_MOVE ioctl which uses uffd to move source
>> into destination buffer while checking the contents of both after
>> the move. After the operation the content of the destination buffer
>> should match the original source buffer's content while the source
>> buffer should be zeroed. Separate tests are designed for PMD aligned and
>> unaligned cases because they utilize different code paths in the kernel.
>>
>> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
>> ---
>>   tools/testing/selftests/mm/uffd-common.c     |  24 +++
>>   tools/testing/selftests/mm/uffd-common.h     |   1 +
>>   tools/testing/selftests/mm/uffd-unit-tests.c | 189 +++++++++++++++++++
>>   3 files changed, 214 insertions(+)
>>
>> diff --git a/tools/testing/selftests/mm/uffd-common.c b/tools/testing/selftests/mm/uffd-common.c
>> index fb3bbc77fd00..b0ac0ec2356d 100644
>> --- a/tools/testing/selftests/mm/uffd-common.c
>> +++ b/tools/testing/selftests/mm/uffd-common.c
>> @@ -631,6 +631,30 @@ int copy_page(int ufd, unsigned long offset, bool wp)
>>   	return __copy_page(ufd, offset, false, wp);
>>   }
>>   
>> +int move_page(int ufd, unsigned long offset, unsigned long len)
>> +{
>> +	struct uffdio_move uffdio_move;
>> +
>> +	if (offset + len > nr_pages * page_size)
>> +		err("unexpected offset %lu and length %lu\n", offset, len);
>> +	uffdio_move.dst = (unsigned long) area_dst + offset;
>> +	uffdio_move.src = (unsigned long) area_src + offset;
>> +	uffdio_move.len = len;
>> +	uffdio_move.mode = UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES;
>> +	uffdio_move.move = 0;
>> +	if (ioctl(ufd, UFFDIO_MOVE, &uffdio_move)) {
>> +		/* real retval in uffdio_move.move */
>> +		if (uffdio_move.move != -EEXIST)
>> +			err("UFFDIO_MOVE error: %"PRId64,
>> +			    (int64_t)uffdio_move.move);
> 
> Hi Suren,
> 
> FYI this error is triggering in mm-unstable (715b67adf4c8):
> 
> Testing move-pmd on anon... ERROR: UFFDIO_MOVE error: -16 (errno=16,
> @uffd-common.c:648)
> 
> I'm running in a VM on Apple M2 (arm64). I haven't debugged any further, but
> happy to go deeper if you can direct.

Does it trigger reliably? Which pagesize is that kernel using?

I can spot that uffd_move_pmd_test()/uffd_move_pmd_handle_fault() uses 
default_huge_page_size(), which reads the default hugetlb size.

That, however, does not necessarily correspond to the THP size. That one 
can be obtained using read_pmd_pagesize() in vm_util.c

I quickly scanned the code (still want to take a deeper look), but all 
PAE checks looked sane to me.

I think the issue is folio split handling. I replied to the patch.

-- 
Cheers,

David / dhildenb



  parent reply	other threads:[~2023-12-01 20:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 17:16 [PATCH v5 0/5] userfaultfd move option Suren Baghdasaryan
2023-11-21 17:16 ` [PATCH v5 1/5] mm/rmap: support move to different root anon_vma in folio_move_anon_rmap() Suren Baghdasaryan
2023-11-21 17:16 ` [PATCH v5 2/5] userfaultfd: UFFDIO_MOVE uABI Suren Baghdasaryan
2023-11-21 17:16 ` [PATCH v5 3/5] selftests/mm: call uffd_test_ctx_clear at the end of the test Suren Baghdasaryan
2023-11-21 17:16 ` [PATCH v5 4/5] selftests/mm: add uffd_test_case_ops to allow test case-specific operations Suren Baghdasaryan
2023-11-21 17:16 ` [PATCH v5 5/5] selftests/mm: add UFFDIO_MOVE ioctl test Suren Baghdasaryan
2023-12-01  9:29   ` Ryan Roberts
2023-12-01 16:26     ` Suren Baghdasaryan
2023-12-02  8:02       ` Ryan Roberts
2023-12-01 20:47     ` David Hildenbrand [this message]
2023-12-01 21:59       ` Suren Baghdasaryan
2023-12-02  8:04       ` Ryan Roberts
2023-12-02 10:11         ` David Hildenbrand
2023-12-04  4:09           ` Suren Baghdasaryan
2023-12-04  9:27             ` Ryan Roberts
2023-12-04 16:35               ` Suren Baghdasaryan
2023-12-04 18:27                 ` David Hildenbrand
2023-12-04 18:44                   ` Suren Baghdasaryan
2023-12-05  4:46                     ` Suren Baghdasaryan
2023-12-06  9:21                       ` David Hildenbrand
2023-12-06 10:30                         ` Suren Baghdasaryan
2023-12-06 10:39                           ` Suren Baghdasaryan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a41c759f-78d8-44ed-b708-1bb737a8e6c1@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=bgeffon@google.com \
    --cc=brauner@kernel.org \
    --cc=hughd@google.com \
    --cc=jannh@google.com \
    --cc=jdduke@google.com \
    --cc=kaleshsingh@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lokeshgidra@google.com \
    --cc=mhocko@suse.com \
    --cc=ngeoffray@google.com \
    --cc=peterx@redhat.com \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=zhangpeng362@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox