From: Ackerley Tng <ackerleytng@google.com>
To: kartikey406@gmail.com, seanjc@google.com, pbonzini@redhat.com,
shuah@kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: vannapurve@google.com, Liam.Howlett@oracle.com,
ackerleytng@google.com, akpm@linux-foundation.org,
baohua@kernel.org, baolin.wang@linux.alibaba.com,
david@kernel.org, dev.jain@arm.com, i@maskray.me,
lance.yang@linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, shy828301@gmail.com,
stable@vger.kernel.org,
syzbot+33a04338019ac7e43a44@syzkaller.appspotmail.com,
ziy@nvidia.com
Subject: [PATCH v2 0/2] Test MADV_COLLAPSE on guest_memfd
Date: Fri, 20 Feb 2026 23:54:34 +0000 [thread overview]
Message-ID: <cover.1771630983.git.ackerleytng@google.com> (raw)
syzkaller identified that khugepaged, operating on guest_memfd memory,
could cause guest_memfd folios to get collapsed, leading to a WARNing
during fault [1].
Add selftest to guard against similar regressions.
Changes in v2:
+ Found get_trans_hugepagesz(), which I should have used instead of
adding getpmdsize()
+ Extended tools/testing/selftests/kvm/include/kvm_syscalls.h to add
kvm_madvise()
+ Removed the magic constant address and explained alignment requirements in
comments
+ Refactored gmem_test() macro to expose __gmem_test(), which allows custom
sized guest_memfds for tests. Sean, I didn't add the gmem_test_huge_pmd()
since I'm guessing a test requiring a pmd_sized guest_memfd would probably be
once-off.
PATCH v1 [3] was sent in reply to the fix [2].
[1] https://syzkaller.appspot.com/bug?extid=33a04338019ac7e43a44
[2] https://lore.kernel.org/all/20260214001535.435626-1-kartikey406@gmail.com/
[3] https://lore.kernel.org/all/20260217014402.2554832-1-ackerleytng@google.com/
Ackerley Tng (2):
KVM: selftests: Wrap madvise() to assert success
KVM: selftests: Test MADV_COLLAPSE on guest_memfd
.../testing/selftests/kvm/guest_memfd_test.c | 70 ++++++++++++++++++-
.../selftests/kvm/include/kvm_syscalls.h | 1 +
2 files changed, 68 insertions(+), 3 deletions(-)
base-commit: a95f71ad3e2e224277508e006580c333d0a5fe36
prerequisite-patch-id: e001eecc9215dc0ed28546936f86a5a09e57141e
--
2.53.0.345.g96ddfc5eaa-goog
next reply other threads:[~2026-02-20 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 23:54 Ackerley Tng [this message]
2026-02-20 23:54 ` [PATCH v2 1/2] KVM: selftests: Wrap madvise() to assert success Ackerley Tng
2026-02-23 9:38 ` David Hildenbrand (Arm)
2026-02-20 23:54 ` [PATCH v2 2/2] KVM: selftests: Test MADV_COLLAPSE on guest_memfd Ackerley Tng
2026-03-05 17:08 ` [PATCH v2 0/2] " Sean Christopherson
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=cover.1771630983.git.ackerleytng@google.com \
--to=ackerleytng@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=i@maskray.me \
--cc=kartikey406@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+33a04338019ac7e43a44@syzkaller.appspotmail.com \
--cc=vannapurve@google.com \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.