Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Venkatesh Srinivas <venkateshs@google.com>,
	Christoph Hellwig <hch@infradead.org>,
	Hannes Reinecke <hare@suse.de>,
	Paolo Bonzini <pbonzini@redhat.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 12:31:23 -0700	[thread overview]
Message-ID: <20140613193123.GA25432@kroah.com> (raw)
In-Reply-To: <1402687105.2224.64.camel@dabdike.int.hansenpartnership.com>

On Fri, Jun 13, 2014 at 12:18:25PM -0700, James Bottomley wrote:
> On Fri, 2014-06-13 at 12:15 -0700, Venkatesh Srinivas wrote:
> > On Fri, Jun 13, 2014 at 12:09 PM, James Bottomley
> > <James.Bottomley@hansenpartnership.com> wrote:
> > > On Fri, 2014-06-13 at 11:52 -0700, Christoph Hellwig wrote:
> > >> On Fri, Jun 13, 2014 at 10:58:22AM -0700, Venkatesh Srinivas wrote:
> > >> > 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.
> > >>
> > >> No patch attached.  Nevermind this is not a consdervative fix, but a
> > >> band aid.  The proper fix is to figure out what's actually going on
> > >> here.
> > >>
> > >> >From your trace above it very much looks like a double completion of
> > >> some sort.
> > >>
> > >> I've looked at the virtio-scsi code a bit, and one odd thing it does
> > >> that comes in handy here is that it doesn't really use a traditional
> > >> tag, but rather the address of the scsi command.
> > >
> > > What kernel version?  This is the exact signature of the original USB
> > > REQUEST_SENSE problem.
> > 
> > Mix of kernels, all 3.14-based. Debian 3.14-0.bpo, Gentoo's 3.14,
> > upstream from git as of a few days ago.
> > 
> > Distribution 3.13 and earlier kernels (Debian's 3.2.0-4, Debian
> > 3.13-0.bpo.1, Gentoo 3.13.6) do not hit this issue with the same
> > workload.
> 
> OK, I've no idea what's in distro kernels, so you're looking for this
> fix:
> 
> commit d555a2abf3481f81303d835046a5ec2c4fb3ca8e
> Author: James Bottomley <JBottomley@Parallels.com>
> Date:   Fri Mar 28 10:50:17 2014 -0700
> 
>     [SCSI] Fix spurious request sense in error handling
> 
> It went into v3.15-rc3.  It looks like it wasn't backported to stable.

That would be because no one asked it to be backported, why didn't you
tag it as such?

greg k-h

  reply	other threads:[~2014-06-13 19:31 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
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 [this message]
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=20140613193123.GA25432@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hare@suse.de \
    --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