All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <jbottomley@parallels.com>,
	linux-scsi@vger.kernel.org, Christoph Hellwig <hch@infradead.com>,
	Ren Mingxin <renmx@cn.fujitsu.com>, Joern Engel <joern@logfs.org>,
	James Smart <james.smart@emulex.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 2/5] scsi: improved eh timeout handler
Date: Tue, 11 Feb 2014 06:01:48 -0800	[thread overview]
Message-ID: <20140211140148.GA1897@infradead.org> (raw)
In-Reply-To: <1384173897-103836-3-git-send-email-hare@suse.de>

Hi Hannes,

I'll need a little reminder how we came to the conclusion that the
cancel_delayed_work in scsi_put_command was safe and we didn't need
a cancel_delayed_work_sync or flush_delayed_work.  I remember we had
that discussion, but it seems that same doesn't apply to the equivalent
call in the blk-mq codepath in my tree.  If you remember anything that
might make my life debugging this a bit easier.


  reply	other threads:[~2014-02-11 14:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 12:44 [PATCHv11 0/5] New EH command timeout handler Hannes Reinecke
2013-11-11 12:44 ` [PATCH 1/5] scsi: Fix erratic device offline during EH Hannes Reinecke
2013-11-11 12:44 ` [PATCH 2/5] scsi: improved eh timeout handler Hannes Reinecke
2014-02-11 14:01   ` Christoph Hellwig [this message]
2014-02-11 14:29     ` Hannes Reinecke
2014-02-12  7:45       ` Christoph Hellwig
2014-02-12  7:49         ` Hannes Reinecke
2013-11-11 12:44 ` [PATCH 3/5] scsi: Unlock accesses to eh_deadline Hannes Reinecke
2013-11-11 12:44 ` [PATCH 4/5] scsi: Set the minimum valid value of 'eh_deadline' as 0 Hannes Reinecke
2013-11-11 12:44 ` [PATCH 5/5] scsi: Update documentation Hannes Reinecke
  -- strict thread matches above, loose matches on Subject: below --
2013-11-05  7:05 [PATCHv10 0/5] New EH command timeout handler Hannes Reinecke
2013-11-05  7:05 ` [PATCH 2/5] scsi: improved eh " Hannes Reinecke
2013-11-05 19:19   ` Mike Christie
2013-11-06  6:48     ` Hannes Reinecke
2013-11-06 17:23       ` Mike Christie
2013-11-07  6:45         ` Hannes Reinecke
2013-11-07 18:33           ` Douglas Gilbert
2013-11-08 15:54             ` Hannes Reinecke
2013-11-09  8:35           ` James Bottomley
2013-11-09 15:27             ` Hannes Reinecke
2013-11-06 14:47     ` Christoph Hellwig
2013-11-07  6:42       ` Hannes Reinecke

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=20140211140148.GA1897@infradead.org \
    --to=hch@infradead.org \
    --cc=hare@suse.de \
    --cc=hch@infradead.com \
    --cc=james.smart@emulex.com \
    --cc=jbottomley@parallels.com \
    --cc=joern@logfs.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=renmx@cn.fujitsu.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 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.