All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takahiro Yasui <tyasui@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: [RFC][PATCH 0/3] dm-raid1: fix deadlock at suspend after suspend was interrupted
Date: Tue, 19 Jan 2010 15:40:55 -0500	[thread overview]
Message-ID: <4B5618D7.4050202@redhat.com> (raw)

Hi,

This is a patch set to fix deadlock on suspending of mirror device.


ISSUE
=====

Suspend procedure on a dm-mirror device could cause deadlock on recovery_count
semaphore.

When mirror_presuspend is called, recovery_count semaphore is acquired in
dm_rh_stop_recovery() to stop recovery routine, but when an signal is caught
in dm_wait_for_completion() or an error occurred in in dm_suspend(),
the suspend process is interrupted without releasing recovery_count semaphore
of a mirror device. This means that another suspend is executed, and then
the suspend process gets stuck at dm_rh_stop_recovery().

When suspend procedure is interrupted, the device should work properly since
the status of the device is not "suspended."


SOLUTION
========

Introduce a target handler, cancel_presuspend, to cancel status changes
done by a target specific presuspend handler.


PATCH SET
=========
    1/3: dm: introduce cancel_presuspend framework
    2/3: dm-raid1: add cancel_presuspend function
    3/3: dm-delay: add cancel_presuspend function


I appreciate your comments.

Thanks,
-- 
Takahiro Yasui
Hitachi Computer Products (America), Inc.

             reply	other threads:[~2010-01-19 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 20:40 Takahiro Yasui [this message]
2010-01-20  2:47 ` [RFC][PATCH 0/3] dm-raid1: fix deadlock at suspend after suspend was interrupted Kiyoshi Ueda
2010-01-20 22:58   ` Takahiro Yasui
2010-01-21  9:20     ` Kiyoshi Ueda
2010-01-22  6:16       ` Takahiro Yasui

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=4B5618D7.4050202@redhat.com \
    --to=tyasui@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.