From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 0/3] Add deleting state check for target messages
Date: Sun, 15 Nov 2009 23:38:48 -0800 [thread overview]
Message-ID: <20091116073848.GA20475@linux.vnet.ibm.com> (raw)
In-Reply-To: <4B00B597.6050905@ct.jp.nec.com>
Kiyoshi Ueda <k-ueda@ct.jp.nec.com> wrote:
> Hi Mike,
>
> On 11/13/2009 05:04 PM +0900, Mike Anderson wrote:
> > 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
>
> Thank you for the patch-set.
> Although I'm not sure this patch-set is really needed after the fix
> of message ioctl during suspend will have been done, I understand
> why you want this patch-set (since issuing message ioctl to a deleting
> device is a bit pointless).
>
Yes this patch set should not be needed post the fix to the message ioctl.
The reduction was aimed at future callers using dm_get_md prior to
DMF_FREEING being set as the dm_table_destroy holders wait would not
proceed until current message operations had completed, but the reduction
of this case is not that important with the other message ioctl changes in
place.
This patch set can be dropped.
> But there is a small window in this patch-set as Malahal described.
> Also, I have some comments below:
> o Please use drivers/md/dm.h instead of include/linux/device-mapper.h
> and don't export symbols, because all accessors you are adding are
> used in only dm-core, no target uses them.
>
> o target_message() can use dm_deleting(), because target_message()
> has a reference to the md.
> We don't need the table function, dm_table_md_deleting(), at all.
>
Thanks for the review tip.
-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com
next prev parent reply other threads:[~2009-11-16 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 8:04 [PATCH 0/3] Add deleting state check for target messages Mike Anderson
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 [this message]
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=20091116073848.GA20475@linux.vnet.ibm.com \
--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.