From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 105311] AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:14.0 address=0x000000fdf9103300 flags=0x0600]
Date: Sat, 24 Sep 2016 19:40:17 +0000 [thread overview]
Message-ID: <bug-105311-28872-x0EGSqGrmN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-105311-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=105311
Vedran Miletić <vedran@miletic.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vedran@miletic.net
--- Comment #14 from Vedran Miletić <vedran@miletic.net> ---
There was a patch posted at [1] which was merged as
commit cbf3ccd09d683abf1cacd36e3640872ee912d99b
Author: Joerg Roedel <jroedel@suse.de>
Date: Tue Oct 20 14:59:36 2015 +0200
iommu/amd: Don't clear DTE flags when modifying it
During device assignment/deassignment the flags in the DTE
get lost, which might cause spurious faults, for example
when the device tries to access the system management range.
Fix this by not clearing the flags with the rest of the DTE.
Reported-by: G. Richard Bellamy <rbellamy@pteradigm.com>
Tested-by: G. Richard Bellamy <rbellamy@pteradigm.com>
Cc: stable@vger.kernel.org
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Can anyone mark this resolved?
[1] https://lists.linuxfoundation.org/pipermail/iommu/2015-October/014682.html
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2016-09-24 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 15:53 [Bug 105311] New: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:14.0 address=0x000000fdf9103300 flags=0x0600] bugzilla-daemon
2015-10-01 15:54 ` [Bug 105311] " bugzilla-daemon
2015-10-01 15:54 ` bugzilla-daemon
2015-10-01 15:55 ` bugzilla-daemon
2015-10-01 15:55 ` bugzilla-daemon
2015-10-03 17:39 ` bugzilla-daemon
2015-10-03 17:42 ` bugzilla-daemon
2015-10-03 17:48 ` bugzilla-daemon
2015-10-03 22:51 ` bugzilla-daemon
2015-10-03 23:39 ` bugzilla-daemon
2015-10-03 23:55 ` bugzilla-daemon
2015-10-04 0:20 ` bugzilla-daemon
2015-10-04 7:24 ` bugzilla-daemon
2015-10-04 7:25 ` bugzilla-daemon
2016-09-24 19:40 ` bugzilla-daemon [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=bug-105311-28872-x0EGSqGrmN@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).