From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Jens Axboe <axboe@fb.com>, Shaohua Li <shli@fb.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stefan Haberland <stefan.haberland@de.ibm.com>
Subject: Re: [PATCH] block: Refine blk_abort_request() documentation
Date: Mon, 11 May 2015 13:44:56 +0200 [thread overview]
Message-ID: <20150511114456.GA5097@lst.de> (raw)
In-Reply-To: <55509060.4010601@sandisk.com>
On Mon, May 11, 2015 at 01:20:00PM +0200, Bart Van Assche wrote:
> Document when it is safe to call this function for blk-mq queues.
Maybe we should move the queue_lock acquisition into blk_abort_request
for the !blk-mq case? libata and libsas already take it just around the
call, an the usage in the dasd driver looks like it only needs
the queue_lock for the blk_abort_request call as well.
next prev parent reply other threads:[~2015-05-11 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 11:20 [PATCH] block: Refine blk_abort_request() documentation Bart Van Assche
2015-05-11 11:44 ` Christoph Hellwig [this message]
2015-05-11 16:58 ` Jens Axboe
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=20150511114456.GA5097@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@fb.com \
--cc=stefan.haberland@de.ibm.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