Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Venkatesh Srinivas <venkateshs@google.com>,
	hch@infradead.org, Paolo Bonzini <pbonzini@redhat.com>,
	JBottomley@parallels.com, linux-scsi@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: virtio-scsi issues duplicate tags when async_abort is enabled
Date: Fri, 13 Jun 2014 20:37:43 +0200	[thread overview]
Message-ID: <539B44F7.6050803@suse.de> (raw)
In-Reply-To: <CAHdzE-8k6A6kVB7DnOc6_XKg6DANLRFmP9+f4oXE1vPoLhOK=g@mail.gmail.com>

On 06/13/2014 07:58 PM, Venkatesh Srinivas wrote:
> Hi,
>
> In Linux 3.14+, SCSI timeouts are handled first without invoking EH;
> this behavior is on by default but can be disabled with the
> per-shost-template no_async_abort flag.
>
> When a SCSI target is attached to a virtio-scsi HBA and is under I/O
> stress (lots of concurrent I/O + some I/O running slowly), we see
> Linux issue commands with duplicate tags, sometimes with tags matching
> commands which are in the process of being aborted; we see this
> readily in the Google Compute Engine hypervisor.
>
> This behaviour is not seen on Linux <= 3.13 and is not seen if 3.14's
> virtio_scsi driver has no_async_abort set to 1.
>
> An ordering we have seen, from the device perspective:
> t0: I/O with tag 18446612135224154432 issued
> t1: TMF Abort for tag 18446612135224154432
> t2: Another I/O with the same tag, 18446612135224154432, issued; same
> offset/size as at t0
> [neither the t0 I/O nor the TMF ABORT have yet returned!]
>
> Another ordering we have seen, from the device perspective:
> t0: I/O with tag 18446612135454768576 issued
> t1: TMF ABORT for tag 18446612135454768576
> t2: I/O 18446612135454768576 completes with appropriate cancelled status
> t3: TMF ABORT completes with OK status
> t4: New I/O with tag 18446612135454768576, matching size/offset as t0
> t5...: [Some other I/Os issued to the same SCSI target]
> t6...: [TMF ABORT for one of the new I/Os; proper return sequence]
> t7...: New I/O with tag 18446612135454768576.
>    [Tag 18446612135454768576 has neither completed nor has it been
> aborted by Linux.]
>
> CC-ing stable as 3.14 and 3.15 are affected; a conservative fix is to
> enable no_async_abort until the problem is better-understood.
>
Paolo, you had some fixes for virtio_scsi which should solve this, right?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-06-13 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 17:58 virtio-scsi issues duplicate tags when async_abort is enabled Venkatesh Srinivas
2014-06-13 18:37 ` Hannes Reinecke [this message]
2014-06-13 18:43   ` Venkatesh Srinivas
2014-06-13 18:52 ` Christoph Hellwig
2014-06-13 19:09   ` James Bottomley
2014-06-13 19:15     ` Venkatesh Srinivas
2014-06-13 19:18       ` James Bottomley
2014-06-13 19:31         ` Greg KH
2014-06-13 19:29           ` James Bottomley
2014-06-14  2:50         ` Venkatesh Srinivas
2014-06-14 15:10           ` James Bottomley

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=539B44F7.6050803@suse.de \
    --to=hare@suse.de \
    --cc=JBottomley@parallels.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=venkateshs@google.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