All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: emilne@redhat.com, Helge Deller <deller@gmx.de>
Cc: "linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: kernel BUG in drivers/scsi/53c700.c:1129
Date: Fri, 10 Jun 2016 14:01:13 -0700	[thread overview]
Message-ID: <1465592473.2224.52.camel@HansenPartnership.com> (raw)
In-Reply-To: <1465592285.20724.173.camel@localhost.localdomain>

On Fri, 2016-06-10 at 16:58 -0400, Ewan D. Milne wrote:
> I'm not sure if this is the problem, but the tagging changes to
> scsi_tcq.h may have altered the 53c700 driver's assumptions.
> In one case it sets sdev->current_cmnd and then some of the
> tagging calls would return it if the tag was SCSI_NO_TAG.
> 
> NCR_700_queuecommand_lck() does:
> 
>         if ((hostdata->tag_negotiated & (1<<scmd_id(SCp))) &&
>             SCp->device->simple_tags) {
>                 slot->tag = SCp->request->tag;
>                 CDEBUG(KERN_DEBUG, SCp, "sending out tag %d, slot
> %p\n",
>                        slot->tag, slot);
>         } else {
>                 slot->tag = SCSI_NO_TAG;
>                 /* must populate current_cmnd for scsi_host_find_tag
> to
> work */
>                 SCp->device->current_cmnd = SCp;
>         }

Thanks ... I was just about to look for something this.  I'd got to
interpreting the script as reselected with tag information present and
then trying to look the command up with no tag present, hence the
BUG().

James



  reply	other threads:[~2016-06-10 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 19:36 kernel BUG in drivers/scsi/53c700.c:1129 Helge Deller
2016-06-09 22:23 ` James Bottomley
2016-06-10 20:25   ` Helge Deller
2016-06-10 20:58     ` Ewan D. Milne
2016-06-10 21:01       ` James Bottomley [this message]
2016-06-10 21:33         ` James Bottomley
2016-06-10 21:43           ` James Bottomley
2016-06-13  8:09             ` Christoph Hellwig
2016-06-10 21:46           ` Helge Deller

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=1465592473.2224.52.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=deller@gmx.de \
    --cc=emilne@redhat.com \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.