public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Steven Haber <steven@qumulo.com>,
	linux-scsi@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: SCSI eats error from flush failure during hot plug
Date: Thu, 26 Jun 2014 14:52:56 -0400	[thread overview]
Message-ID: <1403808776.6440.14.camel@dabdike> (raw)
In-Reply-To: <20140626150832.GA31800@infradead.org>

On Thu, 2014-06-26 at 08:08 -0700, Christoph Hellwig wrote:
> On Thu, Jun 26, 2014 at 11:04:56AM -0400, James Bottomley wrote:
> > Right, but look what we do for the specials.  The only difference is the
> > ULD has a hook to generate the CDB.  For everything else we follow the
> > BLOCK_PC path, including error handling and sense data processing.
> 
> No, we don't use the BLOCK_PC path for anything but a tiny bit of setup
> code right now.  We will with your patch, which will cause all kinds of
> behavior change.  See my last mail for the list of differences, which
> includes the introduction of a major memory leak.

OK, I give up, what memory leak (you don't actually mention it in your
emails)?  All memory handling is correctly done in unprep as far as I
can tell.

James



  reply	other threads:[~2014-06-26 18:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 23:52 SCSI eats error from flush failure during hot plug Steven Haber
2014-06-07 19:29 ` James Bottomley
2014-06-09 17:21   ` Steven Haber
2014-06-09 17:29     ` James Bottomley
2014-06-11 13:37       ` Christoph Hellwig
2014-06-19 18:05         ` James Bottomley
2014-06-25 13:13           ` Christoph Hellwig
2014-06-26 14:02             ` James Bottomley
2014-06-26 15:00               ` Christoph Hellwig
2014-06-26 15:04                 ` James Bottomley
2014-06-26 15:08                   ` Christoph Hellwig
2014-06-26 18:52                     ` James Bottomley [this message]
2014-06-27  7:53                       ` Christoph Hellwig
2014-06-26 15:02 ` Christoph Hellwig
2014-06-26 18:13   ` Steven Haber
2014-06-26 18:52   ` James Bottomley
2014-06-27  7:55     ` Christoph Hellwig
     [not found]       ` <CAPK7rjdpxAALA-oLZJ3wDBPc3kr5Nw4jLALLxEaT0zSiAOD+wg@mail.gmail.com>
2014-06-30 18:45         ` Steven Haber
2014-07-01  8:15           ` Christoph Hellwig
2014-07-03 16:57             ` Steven Haber
2014-07-03 17:18               ` Christoph Hellwig
2014-07-09 22:38                 ` James Bottomley
2014-07-10  7:44                   ` Christoph Hellwig
2014-07-17 15:27                   ` Martin K. Petersen

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=1403808776.6440.14.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=steven@qumulo.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