linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Yishai Hadas <yishaih@nvidia.com>, <idok@nvidia.com>
Cc: <alex.sierra@amd.com>, <akpm@linux-foundation.org>,
	jason Gunthorpe <jgg@nvidia.com>,
	"maor Gottlieb" <maorg@nvidia.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: Bug report: vfio over kernel 5.19 - mm area
Date: Mon, 15 Aug 2022 11:52:55 -0600	[thread overview]
Message-ID: <20220815115255.60eaee8b.alex.williamson@redhat.com> (raw)
In-Reply-To: <0e8a0d16-3c6f-a649-44b3-ab960801d90f@nvidia.com>

On Mon, 15 Aug 2022 18:46:40 +0300
Yishai Hadas <yishaih@nvidia.com> wrote:

> On 15/06/2022 17:02, Alex Williamson wrote:
> > On Wed, 15 Jun 2022 13:52:10 +0300
> > Yishai Hadas <yishaih@nvidia.com> wrote:
> >  
> >> Adding some extra relevant people from the MM area.
> >>
> >> On 15/06/2022 13:43, Yishai Hadas wrote:  
> >>> Hi All,
> >>>
> >>> Any idea what could cause the below break in 5.19 ? we run QEMU and
> >>> immediately the machine is stuck.
> >>>
> >>> Once I run, echo l > /proc/sysrq-trigger could see the below task
> >>> which seems to be stuck..
> >>>
> >>> This basic flow worked fine in 5.18.  
> > Spent Friday bisecting this and posted this fix:
> >
> > https://lore.kernel.org/all/165490039431.944052.12458624139225785964.stgit@omen/
> >
> > I expect you're hotting the same.  Thanks,
> >
> > Alex  
> 
> Alex,
> 
> It seems that we got the same bug again in V6.0 RC1 ..
> 
> The below code [1] from commit [2], put back the 'is_zero_pfn()' under 
> the !(..) and seems buggy.
> 
> I would expect the below fix for that [3].
> 
> Alex Sierra,
> 
> Can you please review the below suggested fix for your patch and send a 
> patch for RC2 accordingly ?
> 

https://lore.kernel.org/all/166015037385.760108.16881097713975517242.stgit@omen/

It's in the mm tree, hopefully it'll get pushed in an early rc.  Thanks,

Alex



      reply	other threads:[~2022-08-15 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a99ed393-3b17-887f-a1f8-a288da9108a0@nvidia.com>
2022-06-15 10:52 ` Yishai Hadas
2022-06-15 13:59   ` Joao Martins
2022-06-15 14:02   ` Alex Williamson
2022-06-15 14:14     ` Yi Liu
2022-06-15 14:22       ` Yishai Hadas
2022-08-15 15:46     ` Yishai Hadas
2022-08-15 17:52       ` Alex Williamson [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=20220815115255.60eaee8b.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.sierra@amd.com \
    --cc=idok@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maorg@nvidia.com \
    --cc=yishaih@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