All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikos Tsironis <ntsironis@arrikto.com>
To: snitzer@kernel.org, agk@redhat.com, dm-devel@redhat.com
Cc: ejt@redhat.com, ntsironis@arrikto.com
Subject: [dm-devel] [PATCH 1/2] dm era: allocate in-core writesets when loading metadata
Date: Wed, 18 Jan 2023 14:29:45 +0200	[thread overview]
Message-ID: <20230118122946.20435-2-ntsironis@arrikto.com> (raw)
In-Reply-To: <20230118122946.20435-1-ntsironis@arrikto.com>

Until now, the allocation of the in-core bitmaps was done in pre-resume
by metadata_resize().

In preparation for the next commit, which makes it possible for a
metadata operation, e.g. an era rollover, to run before pre-resume runs,
allocate the in-core bitmaps as part of opening the metadata.

Also, set the number of blocks of the era device in era_ctr() to the
number of blocks in the metadata.

This avoids attempting to resize the metadata every time we create a new
target instance, even if the metadata size hasn't changed.

Fixes: eec40579d8487 ("dm: add era target")
Cc: stable@vger.kernel.org # v3.15+
Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com>
---
 drivers/md/dm-era-target.c | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/drivers/md/dm-era-target.c b/drivers/md/dm-era-target.c
index e92c1afc3677..3332bed2f412 100644
--- a/drivers/md/dm-era-target.c
+++ b/drivers/md/dm-era-target.c
@@ -788,6 +788,7 @@ static int metadata_digest_start(struct era_metadata *md, struct digest *d)
  * High level metadata interface.  Target methods should use these, and not
  * the lower level ones.
  *--------------------------------------------------------------*/
+static void metadata_close(struct era_metadata *md);
 static struct era_metadata *metadata_open(struct block_device *bdev,
 					  sector_t block_size,
 					  bool may_format)
@@ -811,6 +812,24 @@ static struct era_metadata *metadata_open(struct block_device *bdev,
 		return ERR_PTR(r);
 	}
 
+	if (md->nr_blocks == 0)
+		return md;
+
+	/* Allocate in-core writesets */
+	r = writeset_alloc(&md->writesets[0], md->nr_blocks);
+	if (r) {
+		DMERR("%s: writeset_alloc failed for writeset 0", __func__);
+		metadata_close(md);
+		return ERR_PTR(r);
+	}
+
+	r = writeset_alloc(&md->writesets[1], md->nr_blocks);
+	if (r) {
+		DMERR("%s: writeset_alloc failed for writeset 1", __func__);
+		metadata_close(md);
+		return ERR_PTR(r);
+	}
+
 	return md;
 }
 
@@ -1504,6 +1523,7 @@ static int era_ctr(struct dm_target *ti, unsigned argc, char **argv)
 		return PTR_ERR(md);
 	}
 	era->md = md;
+	era->nr_blocks = md->nr_blocks;
 
 	era->wq = alloc_ordered_workqueue("dm-" DM_MSG_PREFIX, WQ_MEM_RECLAIM);
 	if (!era->wq) {
-- 
2.30.2

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


  reply	other threads:[~2023-01-18 12:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 12:29 [dm-devel] [PATCH 0/2] dm era: avoid deadlock when swapping table with dm-era target Nikos Tsironis
2023-01-18 12:29 ` Nikos Tsironis [this message]
2023-01-18 12:29 ` [dm-devel] [PATCH 2/2] dm era: avoid deadlock when swapping table Nikos Tsironis
2023-01-18 16:28 ` [dm-devel] [PATCH 0/2] dm era: avoid deadlock when swapping table with dm-era target Mike Snitzer
2023-01-19  9:36   ` Nikos Tsironis
2023-01-19 12:58     ` Zdenek Kabelac
2023-01-19 14:08       ` Nikos Tsironis
2023-01-23 17:34     ` Mike Snitzer
2023-01-25 12:37       ` Nikos Tsironis
2023-01-26  0:06         ` Mike Snitzer
2023-01-31 11:01           ` Nikos Tsironis
2023-01-31 20:20             ` Mike Snitzer
2023-02-07  8:10               ` Nikos Tsironis
2023-01-25 12:45       ` Nikos Tsironis

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=20230118122946.20435-2-ntsironis@arrikto.com \
    --to=ntsironis@arrikto.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --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 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.