[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] 8b8125: accel/tcg/cputlb: avoid recursive BQL

From: GitHub
Subject: [Qemu-commits] [qemu/qemu] 8b8125: accel/tcg/cputlb: avoid recursive BQL (fixes #1706...
Date: Tue, 26 Sep 2017 11:47:03 -0700

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 8b81253332b5a3f3c67b6462f39caef47a00dd29
  Author: Alex Bennée <address@hidden>
  Date:   2017-09-25 (Mon, 25 Sep 2017)

  Changed paths:
    M accel/tcg/cputlb.c

  Log Message:
  accel/tcg/cputlb: avoid recursive BQL (fixes #1706296)

The mmio path (see exec.c:prepare_mmio_access) already protects itself
against recursive locking and it makes sense to do the same for
io_readx/writex. Otherwise any helper running in the BQL context will
assert when it attempts to write to device memory as in the case of
the bug report.

Reviewed-by: Peter Maydell <address@hidden>
Signed-off-by: Alex Bennée <address@hidden>
CC: Richard Jones <address@hidden>
CC: Paolo Bonzini <address@hidden>
CC: address@hidden
Message-Id: <address@hidden>
Signed-off-by: Richard Henderson <address@hidden>

  Commit: 2509dda283d438970028864dd89871bfe0263c3a
  Author: Peter Maydell <address@hidden>
  Date:   2017-09-26 (Tue, 26 Sep 2017)

  Changed paths:
    M accel/tcg/cputlb.c

  Log Message:
  Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20170925' into staging

BQL bug fix

# gpg: Signature made Mon 25 Sep 2017 23:14:48 BST
# gpg:                using RSA key 0x64DF38E8AF7E215F
# gpg: Good signature from "Richard Henderson <address@hidden>"
# gpg: WARNING: This key is not certified with sufficiently trusted signatures!
# gpg:          It is not certain that the signature belongs to the owner.
# Primary key fingerprint: 7A48 1E78 868B 4DB6 A85A  05C0 64DF 38E8 AF7E 215F

* remotes/rth/tags/pull-tcg-20170925:
  accel/tcg/cputlb: avoid recursive BQL (fixes #1706296)

Signed-off-by: Peter Maydell <address@hidden>

Compare: https://github.com/qemu/qemu/compare/2b521a654cbe...2509dda283d4

reply via email to

[Prev in Thread] Current Thread [Next in Thread]