All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209253] Loss of connectivity on guest after important host <-> guest traffic
Date: Thu, 22 Oct 2020 22:26:32 +0000	[thread overview]
Message-ID: <bug-209253-28872-Pp1pYjHhVO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209253-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209253

--- Comment #5 from Ian Pilcher (arequipeno@gmail.com) ---
Based on my git bisect, it looks like this commit is triggering the WARNING.

commit c49fa6397b6d29ce10c0ae5b2528bb004a14691f
Author: Alex Williamson <alex.williamson@redhat.com>
Date:   Mon Aug 17 11:08:18 2020 -0600

    vfio-pci: Avoid recursive read-lock usage

    [ Upstream commit bc93b9ae0151ae5ad5b8504cdc598428ea99570b ]

    A down_read on memory_lock is held when performing read/write accesses
    to MMIO BAR space, including across the copy_to/from_user() callouts
    which may fault.  If the user buffer for these copies resides in an
    mmap of device MMIO space, the mmap fault handler will acquire a
    recursive read-lock on memory_lock.  Avoid this by reducing the lock
    granularity.  Sequential accesses requiring multiple ioread/iowrite
    cycles are expected to be rare, therefore typical accesses should not
    see additional overhead.

    VGA MMIO accesses are expected to be non-fatal regardless of the PCI
    memory enable bit to allow legacy probing, this behavior remains with
    a comment added.  ioeventfds are now included in memory access testing,
    with writes dropped while memory space is disabled.

    Fixes: abafbc551fdd ("vfio-pci: Invalidate mmaps and block MMIO access on
disabled memory")
    Reported-by: Zhiyi Guo <zhguo@redhat.com>
    Tested-by: Zhiyi Guo <zhguo@redhat.com>
    Reviewed-by: Cornelia Huck <cohuck@redhat.com>
    Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/vfio/pci/vfio_pci_private.h |   2 +
 drivers/vfio/pci/vfio_pci_rdwr.c    | 120 ++++++++++++++++++++++++++++--------
 2 files changed, 98 insertions(+), 24 deletions(-)

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bc93b9ae0151ae5ad5b8504cdc598428ea99570b

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-10-22 22:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 18:39 [Bug 209253] New: Loss of connectivity on guest after important host <-> guest traffic bugzilla-daemon
2020-10-12  0:07 ` [Bug 209253] " bugzilla-daemon
2020-10-17 15:59 ` bugzilla-daemon
2020-10-20 14:28 ` bugzilla-daemon
2020-10-22 16:14 ` bugzilla-daemon
2020-10-22 22:26 ` bugzilla-daemon [this message]
2020-10-23  8:40 ` bugzilla-daemon
2020-10-23 18:23 ` bugzilla-daemon
2020-10-23 19:05 ` bugzilla-daemon
2020-10-23 22:28 ` bugzilla-daemon
2020-10-27 12:51 ` bugzilla-daemon
2020-10-28 17:12 ` bugzilla-daemon
2020-10-28 20:35 ` bugzilla-daemon
2020-10-28 20:37 ` bugzilla-daemon
2020-10-28 20:52 ` bugzilla-daemon
2020-10-28 23:41 ` bugzilla-daemon
2020-10-30 22:13 ` bugzilla-daemon
2020-10-30 22:53 ` bugzilla-daemon
2020-11-10 18:35 ` bugzilla-daemon
2020-11-10 18:52 ` bugzilla-daemon
2020-11-10 22:43 ` bugzilla-daemon
2020-11-16 11:21 ` bugzilla-daemon
2020-12-04 22:49 ` bugzilla-daemon

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-209253-28872-Pp1pYjHhVO@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 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.