From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Alex Williamson
<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: BUG: unable to handle kernel paging request with v4.3-rc4
Date: Fri, 9 Oct 2015 17:34:40 +0200 [thread overview]
Message-ID: <20151009153440.GE27420@8bytes.org> (raw)
In-Reply-To: <1444404640.4059.219.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Fri, Oct 09, 2015 at 09:30:40AM -0600, Alex Williamson wrote:
> I have not seen this one yet. There literally have been no changes for
> vfio in 4.3, so if this is new, it may be collateral from changes
> elsewhere. 32bit devices really shouldn't make any difference to vfio,
> I'll see if I can reproduce it myself though. Thanks,
Great, thanks. It looks like some sort of memory corruption to me. What
I did was trying to assign the 32bit dev together with its PCI bridge.
Probing the bridge in VFIO fails due to the first check in the probe
function and then I get the oops.
I also tried assigning other bridges, or only the bridge to the 32bit
bus, but this did not trigger the oops (but fails too, as it should).
I'll also try to debug this more.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
kvm@vger.kernel.org
Subject: Re: BUG: unable to handle kernel paging request with v4.3-rc4
Date: Fri, 9 Oct 2015 17:34:40 +0200 [thread overview]
Message-ID: <20151009153440.GE27420@8bytes.org> (raw)
In-Reply-To: <1444404640.4059.219.camel@redhat.com>
On Fri, Oct 09, 2015 at 09:30:40AM -0600, Alex Williamson wrote:
> I have not seen this one yet. There literally have been no changes for
> vfio in 4.3, so if this is new, it may be collateral from changes
> elsewhere. 32bit devices really shouldn't make any difference to vfio,
> I'll see if I can reproduce it myself though. Thanks,
Great, thanks. It looks like some sort of memory corruption to me. What
I did was trying to assign the 32bit dev together with its PCI bridge.
Probing the bridge in VFIO fails due to the first check in the probe
function and then I get the oops.
I also tried assigning other bridges, or only the bridge to the 32bit
bus, but this did not trigger the oops (but fails too, as it should).
I'll also try to debug this more.
Joerg
next prev parent reply other threads:[~2015-10-09 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 14:58 BUG: unable to handle kernel paging request with v4.3-rc4 Joerg Roedel
2015-10-09 14:58 ` Joerg Roedel
[not found] ` <20151009145827.GB27420-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-10-09 15:30 ` Alex Williamson
2015-10-09 15:30 ` Alex Williamson
[not found] ` <1444404640.4059.219.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-09 15:34 ` Joerg Roedel [this message]
2015-10-09 15:34 ` Joerg Roedel
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=20151009153440.GE27420@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.