From: Milan Broz <gmazyland@gmail.com>
To: Salvatore Bonaccorso <carnil@debian.org>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "David Howells" <dhowells@redhat.com>,
"Christoph Hellwig" <hch@infradead.org>,
"David Hildenbrand" <david@redhat.com>,
"Lorenzo Stoakes" <lstoakes@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Matthew Wilcox" <willy@infradead.org>, "Jan Kara" <jack@suse.cz>,
"Jeff Layton" <jlayton@kernel.org>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Logan Gunthorpe" <logang@deltatee.com>,
"Hillf Danton" <hdanton@sina.com>,
"Christian Brauner" <brauner@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Sasha Levin" <sashal@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
regressions@lists.linux.dev,
"stable@vger.kernel.org Bernd Rinn" <bb@rinn.ch>,
"Karri Hämäläinen" <kh.bugreport@outlook.com>,
"Cameron Davidson" <bugs@davidsoncj.id.au>,
Markus <markus@fritz.box>
Subject: Re: [regression 6.1.y] Regression from 476c1dfefab8 ("mm: Don't pin ZERO_PAGE in pin_user_pages()") with pci-passthrough for both KVM VMs and booting in xen DomU
Date: Thu, 17 Apr 2025 07:14:28 +0200 [thread overview]
Message-ID: <060f3d14-e669-4485-98d1-fb89f8cef79b@gmail.com> (raw)
In-Reply-To: <aAAmQ-sRQhejItzQ@eldamar.lan>
On 4/16/25 11:50 PM, Salvatore Bonaccorso wrote:
> Hi Alex,
>
> On Wed, Apr 16, 2025 at 02:26:45PM -0600, Alex Williamson wrote:
>> On Tue, 15 Apr 2025 20:59:19 +0200
>> Salvatore Bonaccorso <carnil@debian.org> wrote:
>>
>>> Hi
>>>
>>> [Apologies if this has been reported already but I have not found an
>>> already filled corresponding report]
>>>
>>> After updating from the 6.1.129 based version to 6.1.133, various
>>> users have reported that their VMs do not boot anymore up (both KVM
>>> and under Xen) if pci-passthrough is involved. The reports are at:
>>>
>>> https://bugs.debian.org/1102889
>>> https://bugs.debian.org/1102914
>>> https://bugs.debian.org/1103153
>>>
>>> Milan Broz bisected the issues and found that the commit introducing
>>> the problems can be tracked down to backport of c8070b787519 ("mm:
>>> Don't pin ZERO_PAGE in pin_user_pages()") from 6.5-rc1 which got
>>> backported as 476c1dfefab8 ("mm: Don't pin ZERO_PAGE in
>>> pin_user_pages()") in 6.1.130. See https://bugs.debian.org/1102914#60
>>>
>>> #regzbot introduced: 476c1dfefab8b98ae9c3e3ad283c2ac10d30c774
>>>
>>> 476c1dfefab8b98ae9c3e3ad283c2ac10d30c774 is the first bad commit
>>> commit 476c1dfefab8b98ae9c3e3ad283c2ac10d30c774
>>> Author: David Howells <dhowells@redhat.com>
>>> Date: Fri May 26 22:41:40 2023 +0100
>>>
>>> mm: Don't pin ZERO_PAGE in pin_user_pages()
>>>
>>> [ Upstream commit c8070b78751955e59b42457b974bea4a4fe00187 ]
>>
>> It's a bad backport, I've debugged and posted the fix for stable here:
>>
>> https://lore.kernel.org/all/20250416202441.3911142-1-alex.williamson@redhat.com/
>
> Thank you, that worked (replying here as well mainly to fix my mistake
> in the CC to stable@vger.kernel.org, which got truncated to
> table@vger.kernel.org in my initial submission).
I can also confirm the fix works, thanks for the quick response!
Tested-by: Milan Broz <gmazyland@gmail.com>
Milan
prev parent reply other threads:[~2025-04-17 5:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 18:59 Salvatore Bonaccorso
2025-04-15 19:07 ` Salvatore Bonaccorso
2025-04-15 19:11 ` Milan Broz
2025-04-16 20:26 ` Alex Williamson
2025-04-16 21:50 ` Salvatore Bonaccorso
2025-04-17 5:14 ` Milan Broz [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=060f3d14-e669-4485-98d1-fb89f8cef79b@gmail.com \
--to=gmazyland@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=bb@rinn.ch \
--cc=brauner@kernel.org \
--cc=bugs@davidsoncj.id.au \
--cc=carnil@debian.org \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=jgg@nvidia.com \
--cc=jlayton@kernel.org \
--cc=kh.bugreport@outlook.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=lstoakes@gmail.com \
--cc=markus@fritz.box \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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