From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: Alasdair Kergon <agk@redhat.com>
Cc: Christof Schmitt <christof.schmitt@de.ibm.com>,
device-mapper development <dm-devel@redhat.com>
Subject: [PATCH 3/8] dm core: reject I/O violating new queue limits
Date: Wed, 18 Mar 2009 17:53:09 +0900 [thread overview]
Message-ID: <49C0B675.6000905@ct.jp.nec.com> (raw)
In-Reply-To: <49C0B474.4000204@ct.jp.nec.com>
This patch detects requests violating the queue limitations
and rejects them.
The same limitation checks are done when requests are submitted
to the queue by blk_insert_cloned_request().
However, such violation can happen if a table is swapped and
the queue limitations are shrunk while some requests are
in the queue.
Since struct request is a reliable one in the block layer and
device drivers, dispatching such requests is pretty dangerous.
(e.g. it may cause kernel panic easily.)
So avoid to dispatch such problematic requests in request-based dm.
Signed-off-by: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
Cc: Alasdair G Kergon <agk@redhat.com>
---
drivers/md/dm.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
Index: 2.6.29-rc8/drivers/md/dm.c
===================================================================
--- 2.6.29-rc8.orig/drivers/md/dm.c
+++ 2.6.29-rc8/drivers/md/dm.c
@@ -1492,6 +1492,30 @@ static void map_request(struct dm_target
dm_get(md);
tio->ti = ti;
+
+ /*
+ * Although submitted requests to the md->queue are checked against
+ * the table/queue limitations at the submission time, the limitations
+ * may be changed by a table swapping while those already checked
+ * requests are in the md->queue.
+ * If the limitations have been shrunk in such situations, we may be
+ * dispatching requests violating the current limitations here.
+ * Since struct request is a reliable one in the block-layer
+ * and device drivers, dispatching such requests is dangerous.
+ * (e.g. it may cause kernel panic easily.)
+ * Avoid to dispatch such problematic requests in request-based dm.
+ *
+ * Since dm_kill_unmapped_request() expects that tio->ti is correctly
+ * set, this has to be done after the set.
+ */
+ r = blk_rq_check_limits(rq->q, rq);
+ if (unlikely(r)) {
+ DMWARN("violating the queue limitation. the limitation may be"
+ " shrunk while there are some requests in the queue.");
+ dm_kill_unmapped_request(clone, r);
+ return;
+ }
+
r = ti->type->map_rq(ti, clone, &tio->info);
switch (r) {
case DM_MAPIO_SUBMITTED:
next prev parent reply other threads:[~2009-03-18 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 8:44 [PATCH 0/8] request-based dm-multipath (v1) Kiyoshi Ueda
2009-03-18 8:50 ` [PATCH 1/8] dm core: add core functions for request-based dm Kiyoshi Ueda
2009-03-18 8:52 ` [PATCH 2/8] dm core: enable " Kiyoshi Ueda
2009-03-18 8:53 ` Kiyoshi Ueda [this message]
2009-03-18 8:54 ` [PATCH 4/8] dm core: disable interrupt when taking map_lock Kiyoshi Ueda
2009-03-18 8:55 ` [PATCH 5/8] dm-mpath: convert to request-based Kiyoshi Ueda
2009-03-18 8:56 ` [PATCH 6/8] block: add gfp_mask parameter to bio_integrity_clone() Kiyoshi Ueda
2009-03-18 8:57 ` [PATCH 7/8] dm core: pass gfp_mask " Kiyoshi Ueda
2009-03-18 8:58 ` [PATCH 8/8] dm core: add integrity feature to request-based dm Kiyoshi Ueda
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=49C0B675.6000905@ct.jp.nec.com \
--to=k-ueda@ct.jp.nec.com \
--cc=agk@redhat.com \
--cc=christof.schmitt@de.ibm.com \
--cc=dm-devel@redhat.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.