All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: dm-devel@redhat.com
Subject: [PATCH 0/3] Add deleting state check for target messages
Date: Fri, 13 Nov 2009 00:04:22 -0800	[thread overview]
Message-ID: <20091113080422.17412.49305.stgit@localhost.localdomain> (raw)

This patch adds a accessor function that allows determining if a
mapped_device is in the deleting state and then adds this check to the
target_message function. The result of this change would be that all
targets would not be allowed to process messages post a mapped device
entering the deleting state.

As previously described in the email at the archive url provided below the
target_message ioctl can result in new work / activities being started
post the mapped device entering states that new target work could cause
issues.

http://permalink.gmane.org/gmane.linux.kernel.device-mapper.devel/10486

This patch depends on the previous patch that added dm_suspended_check due
to proximity of changes in common files.

---

Mike Anderson (3):
      dm: Add dm_deleting accesor function
      dm: Add accessor dm_table_md_deleting
      dm: Add deleting check to target_message


 drivers/md/dm-ioctl.c         |    6 ++++++
 drivers/md/dm-table.c         |    6 ++++++
 drivers/md/dm.c               |    5 +++++
 include/linux/device-mapper.h |    2 ++
 4 files changed, 19 insertions(+), 0 deletions(-)

--
-andmike

Michael Anderson <andmike@linux.vnet.ibm.com>

             reply	other threads:[~2009-11-13  8:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  8:04 Mike Anderson [this message]
2009-11-13  8:04 ` [PATCH 1/3] dm: Add dm_deleting accesor function Mike Anderson
2009-11-13  8:04 ` [PATCH 2/3] dm: Add accessor dm_table_md_deleting Mike Anderson
2009-11-13  8:04 ` [PATCH 3/3] dm: Add deleting check to target_message Mike Anderson
2009-11-13 18:32   ` malahal
2009-11-16  2:14 ` [PATCH 0/3] Add deleting state check for target messages Kiyoshi Ueda
2009-11-16  7:38   ` Mike Anderson
2009-11-16 15:00     ` Alasdair G Kergon

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=20091113080422.17412.49305.stgit@localhost.localdomain \
    --to=andmike@linux.vnet.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.