qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	pbonzini@redhat.com, fam@euphon.net, thuth@redhat.com,
	lvivier@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH for-6.2 1/2] esp: ensure that async_len is reset to 0 during esp_hard_reset()
Date: Thu, 18 Nov 2021 12:30:12 +0100	[thread overview]
Message-ID: <17121bc4-a2af-4f31-1f23-b512a43dc47a@redhat.com> (raw)
In-Reply-To: <20211118100327.29061-2-mark.cave-ayland@ilande.co.uk>

On 11/18/21 11:03, Mark Cave-Ayland wrote:
> If a reset command is sent after data has been transferred into the SCSI buffer
> ensure that async_len is reset to 0. Otherwise a subsequent TI command assumes
> the SCSI buffer contains data to be transferred to the device causing it to
> dereference the stale async_buf pointer.
> 
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> Fixes: https://gitlab.com/qemu-project/qemu/-/issues/724
> ---
>  hw/scsi/esp.c | 1 +
>  1 file changed, 1 insertion(+)

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>




  reply	other threads:[~2021-11-18 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 10:03 [PATCH for-6.2 0/2] esp: add fix for reset before transfer Mark Cave-Ayland
2021-11-18 10:03 ` [PATCH for-6.2 1/2] esp: ensure that async_len is reset to 0 during esp_hard_reset() Mark Cave-Ayland
2021-11-18 11:30   ` Philippe Mathieu-Daudé [this message]
2021-11-18 10:03 ` [PATCH for-6.2 2/2] qtest/am53c974-test: add test for reset before transfer Mark Cave-Ayland
2021-11-18 10:19   ` Thomas Huth
2021-11-19  9:14 ` [PATCH for-6.2 0/2] esp: add fix " Paolo Bonzini

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=17121bc4-a2af-4f31-1f23-b512a43dc47a@redhat.com \
    --to=philmd@redhat.com \
    --cc=fam@euphon.net \
    --cc=lvivier@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).