From: Vlastimil Babka <vbabka@suse.cz>
To: David Hildenbrand <david@redhat.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Alex Sierra <alex.sierra@amd.com>,
Alistair Popple <apopple@nvidia.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Ralph Campbell <rcampbell@nvidia.com>,
Felix Kuehling <Felix.Kuehling@amd.com>,
Christoph Hellwig <hch@lst.de>,
Jerome Glisse <jglisse@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: hmm_test issues with latest mainline
Date: Fri, 14 Oct 2022 08:45:50 +0200 [thread overview]
Message-ID: <a33f4e26-4436-43ad-9aef-cd7b02e3fb14@suse.cz> (raw)
In-Reply-To: <ecebc355-eff8-0046-3749-8738ed1954de@redhat.com>
On 10/13/22 20:00, David Hildenbrand wrote:
>>>>> When did that test start failing? Was it still ok for 6.0?
>>>
>>> Didn't test yet, will try, in case it's my system/config specific thing.
>>
>> So it's actually all the same with v6.0 for me. The infinite loops, the test
>> failures, the misreported SKIPs.
>>
>> # RUN hmm.hmm_device_private.exclusive ...
>> # hmm-tests.c:1673:exclusive:Expected ret (-16) == 0 (0)
>> hmm close returned (-1) fd is (3)
>> # exclusive: Test failed at step #1
>> # FAIL hmm.hmm_device_private.exclusive
>> not ok 20 hmm.hmm_device_private.exclusive
>> # RUN hmm.hmm_device_private.exclusive_mprotect ...
>> # hmm-tests.c:1727:exclusive_mprotect:Expected ret (-16) == 0 (0)
>> hmm close returned (-1) fd is (3)
>> # exclusive_mprotect: Test failed at step #1
>> # FAIL hmm.hmm_device_private.exclusive_mprotect
>> not ok 21 hmm.hmm_device_private.exclusive_mprotect
>> # RUN hmm.hmm_device_private.exclusive_cow ...
>> # hmm-tests.c:1780:exclusive_cow:Expected ret (-16) == 0 (0)
>> hmm close returned (-1) fd is (3)
>> # exclusive_cow: Test failed at step #1
>> # FAIL hmm.hmm_device_private.exclusive_cow
>> not ok 22 hmm.hmm_device_private.exclusive_cow
>>
>
> Is the kernel compiled with support. I have the feeling that we might simply
> miss kernel support and it's not handled gracefully ...
If you mean CONFIG_DEVICE_PRIVATE=y then it's there. Couldn't find anything
relevant that wouldn't be enabled.
next prev parent reply other threads:[~2022-10-14 6:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 16:54 Vlastimil Babka
2022-10-13 17:01 ` David Hildenbrand
2022-10-13 17:10 ` Shuah Khan
2022-10-13 17:12 ` Vlastimil Babka
2022-10-13 17:29 ` Shuah Khan
2022-10-13 17:45 ` Vlastimil Babka
2022-10-13 18:00 ` David Hildenbrand
2022-10-13 19:38 ` Shuah Khan
2022-10-13 19:43 ` Vlastimil Babka
2022-10-14 1:45 ` Alistair Popple
2022-10-14 3:21 ` Alistair Popple
2022-10-14 6:53 ` Vlastimil Babka
2022-10-14 6:45 ` Vlastimil Babka [this message]
2022-10-13 17:03 ` Shuah Khan
2022-10-13 17:10 ` Vlastimil Babka
2022-10-14 12:01 ` Jason Gunthorpe
2022-10-14 15:03 ` Felix Kuehling
2022-10-14 15:47 ` Jason Gunthorpe
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=a33f4e26-4436-43ad-9aef-cd7b02e3fb14@suse.cz \
--to=vbabka@suse.cz \
--cc=Felix.Kuehling@amd.com \
--cc=alex.sierra@amd.com \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=jglisse@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rcampbell@nvidia.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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