From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christof Schmitt <christof.schmitt@de.ibm.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH 6/7] dm core: disable interrupt when taking map_lock
Date: Fri, 24 Apr 2009 11:00:10 +0200 [thread overview]
Message-ID: <49F17F9A.9040409@suse.de> (raw)
In-Reply-To: <49F17530.2060701@ct.jp.nec.com>
Kiyoshi Ueda wrote:
> This patch disables interrupt when taking map_lock to prevent
> needless lockdep warnings in request-based dm.
>
> request-based dm takes map_lock after taking queue_lock with
> disabling interrupt:
> spin_lock_irqsave(queue_lock)
> q->request_fn() == dm_request_fn()
> => dm_get_table()
> => read_lock(map_lock)
> while queue_lock could be taken in interrupt context.
>
> So lockdep warns that a deadlock can happen:
> write_lock(map_lock)
> <interrupt>
> spin_lock_irqsave(queue_lock)
> q->request_fn() == dm_request_fn()
> => dm_get_table()
> => read_lock(map_lock)
>
> Currently there is no such code path in request-based dm where
> q->request_fn() is called from interrupt context, so no such deadlock
> happens.
> But such warning messages confuse users, so prevent them by disabling
> interrupt when taking map_lock.
>
>
> Signed-off-by: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
> Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
Acked-by: Hannes Reinecke <hare@suse.de>
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)
next prev parent reply other threads:[~2009-04-24 9:00 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
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 [this message]
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=49F17F9A.9040409@suse.de \
--to=hare@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox