From: Hou Tao <houtao1@huawei.com>
To: Hou Tao <houtao@huaweicloud.com>, <dm-devel@redhat.com>
Cc: Mike Snitzer <snitzer@kernel.org>, <linux-kernel@vger.kernel.org>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: [dm-devel] [PATCH] dm: remove unnecessary check when using dm_get_mdptr()
Date: Wed, 18 Jan 2023 21:16:41 +0800 [thread overview]
Message-ID: <e7fcd9fd-a882-2a97-a072-faf09441efbe@huawei.com> (raw)
In-Reply-To: <20221216042353.3132139-1-houtao@huaweicloud.com>
ping ?
On 12/16/2022 12:23 PM, Hou Tao wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> __hash_remove() removes hash_cell with _hash_lock locked, so acquiring
> _hash_lock can guarantee no-NULL hc returned from dm_get_mdptr() must
> have not been removed and hc->md must still be md.
>
> __hash_remove() also acquires dm_hash_cells_mutex before setting mdptr
> as NULL, so in dm_copy_name_and_uuid() after acquiring
> dm_hash_cells_mutex and ensuring returned hc is not NULL, the returned
> hc must still be alive and hc->md must still be md.
>
> So removing these unnecessary hc->md != md checks when using
> dm_get_mdptr() with _hash_lock or dm_hash_cells_mutex acquired.
>
> Signed-off-by: Hou Tao <houtao1@huawei.com>
> ---
> drivers/md/dm-ioctl.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/md/dm-ioctl.c b/drivers/md/dm-ioctl.c
> index 3bfc1583c20a..2a86524661d1 100644
> --- a/drivers/md/dm-ioctl.c
> +++ b/drivers/md/dm-ioctl.c
> @@ -772,7 +772,7 @@ static struct dm_table *dm_get_inactive_table(struct mapped_device *md, int *src
>
> down_read(&_hash_lock);
> hc = dm_get_mdptr(md);
> - if (!hc || hc->md != md) {
> + if (!hc) {
> DMERR("device has been removed from the dev hash table.");
> goto out;
> }
> @@ -1476,7 +1476,7 @@ static int table_load(struct file *filp, struct dm_ioctl *param, size_t param_si
> /* stage inactive table */
> down_write(&_hash_lock);
> hc = dm_get_mdptr(md);
> - if (!hc || hc->md != md) {
> + if (!hc) {
> DMERR("device has been removed from the dev hash table.");
> up_write(&_hash_lock);
> r = -ENXIO;
> @@ -2128,7 +2128,7 @@ int dm_copy_name_and_uuid(struct mapped_device *md, char *name, char *uuid)
>
> mutex_lock(&dm_hash_cells_mutex);
> hc = dm_get_mdptr(md);
> - if (!hc || hc->md != md) {
> + if (!hc) {
> r = -ENXIO;
> goto out;
> }
next prev parent reply other threads:[~2023-01-18 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 4:23 Hou Tao
2023-01-18 13:16 ` Hou Tao [this message]
2023-01-31 1:44 ` [dm-devel] " Hou Tao
2023-02-17 11:49 ` Hou Tao
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=e7fcd9fd-a882-2a97-a072-faf09441efbe@huawei.com \
--to=houtao1@huawei.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=houtao@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@kernel.org \
/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
all inboxes | Powered by JetHome®