All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH 5/7] dm core: reject I/O violating new queue limits
Date: Fri, 24 Apr 2009 10:59:32 +0200	[thread overview]
Message-ID: <49F17F74.6010307@suse.de> (raw)
In-Reply-To: <49F17510.7010805@ct.jp.nec.com>

Hi Kiyoshi,

Kiyoshi Ueda wrote:
> 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.
> 
This patch actually triggers accidentally during a no-paths scenario;
multipathing seems to flush all device details once all paths are gone,
so it'll fall back to the system defaults.
And then this check will trigger and kill all queued I/Os. Not good.

So either we fix device-mapper to keep the device details even for
the all-paths down scenario (basically we'd have to copy the device
details into the target_io structures and use that for comparison)
or we should rather not check here.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2009-04-24  8:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24  8:10 [PATCH 0/7] request-based dm-multipath (v2) Kiyoshi Ueda
2009-04-24  8:12 ` [PATCH 1/7] dm core: add core functions for request-based dm Kiyoshi Ueda
2009-04-24  8:45   ` Hannes Reinecke
2009-04-24  8:13 ` [PATCH 2/7] dm core: add integrity feature to " Kiyoshi Ueda
2009-04-24  8:46   ` Hannes Reinecke
2009-04-24  8:14 ` [PATCH 3/7] dm core: enable " Kiyoshi Ueda
2009-04-24  8:50   ` Hannes Reinecke
2009-04-24  8:14 ` [PATCH 4/7] dm core: don't set QUEUE_ORDERED_DRAIN for " Kiyoshi Ueda
2009-04-24  8:51   ` Hannes Reinecke
2009-04-24  8:15 ` [PATCH 5/7] dm core: reject I/O violating new queue limits Kiyoshi Ueda
2009-04-24  8:59   ` Hannes Reinecke [this message]
2009-04-28  7:49     ` Kiyoshi Ueda
2009-06-23  5:46       ` Kiyoshi Ueda
2009-04-24  8:15 ` [PATCH 6/7] dm core: disable interrupt when taking map_lock Kiyoshi Ueda
2009-04-24  9:00   ` Hannes Reinecke
2009-04-24 11:50   ` Christof Schmitt
2009-04-24  8:16 ` [PATCH 7/7] dm-mpath: convert to request-based Kiyoshi Ueda
2009-04-24  9:04   ` 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=49F17F74.6010307@suse.de \
    --to=hare@suse.de \
    --cc=agk@redhat.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.