qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, "Michael S. Tsirkin" <mst@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PULL 0/1] Block patches
Date: Mon, 27 Oct 2025 15:05:13 -0400	[thread overview]
Message-ID: <20251027190514.36991-1-stefanha@redhat.com> (raw)

The following changes since commit 36076d24f04ea9dc3357c0fbe7bb14917375819c:

  Merge tag 'next-pr-pull-request' of https://gitlab.com/berrange/qemu into staging (2025-10-25 10:42:55 +0200)

are available in the Git repository at:

  https://gitlab.com/stefanha/qemu.git tags/block-pull-request

for you to fetch changes up to 6910f04aa646f63a0257f77201ad8ea15992b816:

  hw/scsi: avoid deadlock upon TMF request cancelling with VirtIO (2025-10-27 15:00:45 -0400)

----------------------------------------------------------------
Pull request

Fiona's virtio-scsi TMF deadlock fix.

Paolo: I merged the scsi fix in my block tree, but realize now that it belongs
to the scsi subsystem. Sorry about that, I'll be more careful next time. Please
reply if you want to handle this patch yourself.

----------------------------------------------------------------

Fiona Ebner (1):
  hw/scsi: avoid deadlock upon TMF request cancelling with VirtIO

 hw/scsi/virtio-scsi.c | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

-- 
2.51.0



             reply	other threads:[~2025-10-27 19:07 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 19:05 Stefan Hajnoczi [this message]
2025-10-27 19:05 ` [PULL 1/1] hw/scsi: avoid deadlock upon TMF request cancelling with VirtIO Stefan Hajnoczi
2025-10-28 12:11 ` [PULL 0/1] Block patches Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2025-10-06 14:59 Stefan Hajnoczi
2025-10-06 21:59 ` Richard Henderson
2025-04-30 15:47 Stefan Hajnoczi
2025-04-30 19:04 ` Stefan Hajnoczi
2025-05-01 13:03   ` Peter Maydell
2025-03-06  2:21 Stefan Hajnoczi
2025-03-07  7:18 ` Stefan Hajnoczi
2025-01-30 20:33 Stefan Hajnoczi
2025-02-02 17:49 ` Stefan Hajnoczi
2024-09-17 11:43 Stefan Hajnoczi
2024-09-17 14:48 ` Peter Maydell
2024-08-12 15:55 Stefan Hajnoczi
2024-08-13  5:01 ` Richard Henderson
2024-07-25 20:12 Stefan Hajnoczi
2024-07-26  5:12 ` Richard Henderson
2024-04-29 13:43 Stefan Hajnoczi
2024-03-19 15:09 Stefan Hajnoczi
2024-03-19 19:11 ` Peter Maydell
2024-02-06 15:31 Stefan Hajnoczi
2024-02-07 22:19 ` Kevin Wolf
2023-10-16 19:40 Stefan Hajnoczi
2023-10-04 13:53 Stefan Hajnoczi
2023-10-04 18:33 ` Stefan Hajnoczi
2023-07-12 19:36 Stefan Hajnoczi
2023-07-14  6:35 ` Richard Henderson
2023-07-04 15:29 Stefan Hajnoczi
2023-07-06  6:04 ` Richard Henderson
2022-09-22 17:14 Stefan Hajnoczi
2022-09-27 15:04 ` Stefan Hajnoczi
2022-05-25 12:49 Stefan Hajnoczi
2022-05-25 18:35 ` Richard Henderson
2021-12-09 15:21 Stefan Hajnoczi
2021-12-09 15:46 ` Peter Maydell
2021-12-09 16:34   ` Stefan Hajnoczi
2021-12-09 16:53     ` Richard Henderson
2021-12-13  9:33       ` Stefan Hajnoczi
2021-12-14 22:31 ` Richard Henderson
2021-12-06 15:27 Stefan Hajnoczi
2021-12-06 21:16 ` Richard Henderson
2021-10-21 17:41 Stefan Hajnoczi
2021-10-21 22:08 ` Richard Henderson
2021-10-25 10:10   ` Stefan Hajnoczi
2021-03-15  9:51 Stefan Hajnoczi
2021-03-15 22:01 ` Peter Maydell
2021-01-04 14:23 Stefan Hajnoczi
2021-01-04 17:17 ` Peter Maydell
2020-03-17 15:18 Stefan Hajnoczi
2020-03-17 18:32 ` Peter Maydell
2020-01-14  9:30 Stefan Hajnoczi
2020-01-14 16:00 ` Peter Maydell
2019-10-14  8:52 Stefan Hajnoczi
2019-10-15 11:00 ` Peter Maydell

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=20251027190514.36991-1-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=fam@euphon.net \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).