From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
kartikey406@gmail.com, pbonzini@redhat.com, shuah@kernel.org,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
Ackerley Tng <ackerleytng@google.com>
Cc: vannapurve@google.com, Liam.Howlett@oracle.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: Re: [PATCH v2 0/2] Test MADV_COLLAPSE on guest_memfd
Date: Thu, 5 Mar 2026 09:08:27 -0800 [thread overview]
Message-ID: <177272511649.1531226.15957182226632150956.b4-ty@google.com> (raw)
In-Reply-To: <cover.1771630983.git.ackerleytng@google.com>
On Fri, 20 Feb 2026 23:54:34 +0000, Ackerley Tng wrote:
> 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:
>
> [...]
Applied to kvm-x86 selftests, thanks!
[1/2] KVM: selftests: Wrap madvise() to assert success
https://github.com/kvm-x86/linux/commit/58f5d8eebd5c
[2/2] KVM: selftests: Test MADV_COLLAPSE on guest_memfd
https://github.com/kvm-x86/linux/commit/9830209b4ae8
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-03-05 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 23:54 Ackerley Tng
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 ` Sean Christopherson [this message]
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=177272511649.1531226.15957182226632150956.b4-ty@google.com \
--to=seanjc@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=ackerleytng@google.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox