From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Minchan Kim <minchan@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH 2/2] zram: Use a custom key for each zram object.
Date: Fri, 24 Jul 2026 16:52:10 +0900 [thread overview]
Message-ID: <amMY79An64SSBWD4@google.com> (raw)
In-Reply-To: <amLYsq36Qm4Isj63@google.com>
On (26/07/24 12:24), Sergey Senozhatsky wrote:
> > static bool zram_meta_alloc(struct zram *zram, u64 disksize)
> > @@ -1999,7 +1993,8 @@ static bool zram_meta_alloc(struct zram *zram, u64 disksize)
> > if (!huge_class_size)
> > huge_class_size = zs_huge_class_size(zram->mem_pool);
> >
> > - slot_lock_init(zram);
> > + lockdep_register_key(&zram->table_lock_key);
> > + lockdep_init_map(&zram->table_lock_map, "zram->table[index].lock", &zram->table_lock_key, 0);
>
> So I wonder if we can give distinct name, given that it's per-device
> now: "zram%d->table[index].lock" and use zram->disk->first_minor (which
> is a unique device id).
Probably (see below) is not worth it. All those ifdef-s... We used static
name before and didn't have problems with it. So let's just keep doing so
(IOW let's keep not having problems ;))
// completely untested
----
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index 4bfe63a5225d..080012e83f86 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -1956,6 +1956,31 @@ static ssize_t debug_stat_show(struct device *dev,
return ret;
}
+static void zram_lockdep_map_release(struct zram *zram)
+{
+#ifdef CONFIG_LOCKDEP
+ lockdep_unregister_key(&zram->table_lock_key);
+ kfree(zram->table_lock_name);
+#endif
+}
+
+static int zram_lockdep_map_init(struct zram *zram)
+{
+#ifdef CONFIG_LOCKDEP
+ zram->table_lock_name = kasprintf(GFP_KERNEL,
+ "zram%d->table[index].lock",
+ zram->disk->first_minor);
+ if (!zram->table_lock_name)
+ return -ENOMEM;
+
+ lockdep_register_key(&zram->table_lock_key);
+ lockdep_init_map(&zram->table_lock_map, zram->table_lock_name,
+ &zram->table_lock_key, 0);
+#endif
+ return 0;
+}
+
static void zram_meta_free(struct zram *zram, u64 disksize)
{
size_t num_pages = disksize >> PAGE_SHIFT;
@@ -1971,7 +1996,7 @@ static void zram_meta_free(struct zram *zram, u64 disksize)
zs_destroy_pool(zram->mem_pool);
vfree(zram->table);
zram->table = NULL;
- lockdep_unregister_key(&zram->table_lock_key);
+ zram_lockdep_map_release(zram);
}
static bool zram_meta_alloc(struct zram *zram, u64 disksize)
@@ -1990,12 +2015,16 @@ static bool zram_meta_alloc(struct zram *zram, u64 disksize)
return false;
}
+ if (zram_lockdep_map_init(zram)) {
+ zs_destroy_pool(zram->mem_pool);
+ vfree(zram->table);
+ zram->table = NULL;
+ return false;
+ }
+
if (!huge_class_size)
huge_class_size = zs_huge_class_size(zram->mem_pool);
- lockdep_register_key(&zram->table_lock_key);
- lockdep_init_map(&zram->table_lock_map, "zram->table[index].lock", &zram->table_lock_key, 0);
-
return true;
}
diff --git a/drivers/block/zram/zram_drv.h b/drivers/block/zram/zram_drv.h
index 4fddc582f3b8..377832477588 100644
--- a/drivers/block/zram/zram_drv.h
+++ b/drivers/block/zram/zram_drv.h
@@ -106,8 +106,6 @@ struct zram_stats {
struct zram {
struct zram_table_entry *table;
- struct lockdep_map table_lock_map;
- struct lock_class_key table_lock_key;
struct zs_pool *mem_pool;
struct zcomp *comps[ZRAM_MAX_COMPS];
struct zcomp_params params[ZRAM_MAX_COMPS];
@@ -143,5 +141,11 @@ struct zram {
#ifdef CONFIG_ZRAM_MEMORY_TRACKING
struct dentry *debugfs_dir;
#endif
+
+ struct lockdep_map table_lock_map;
+ struct lock_class_key table_lock_key;
+#ifdef CONFIG_LOCKDEP
+ char *table_lock_name;
+#endif
};
#endif
next prev parent reply other threads:[~2026-07-24 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 14:12 [PATCH 0/2] zram: lockmap tweaks Sebastian Andrzej Siewior
2026-07-14 14:12 ` [PATCH 1/2] zram: Move lockmap to be per-zram instead per table Sebastian Andrzej Siewior
2026-07-24 3:25 ` Sergey Senozhatsky
2026-07-14 14:13 ` [PATCH 2/2] zram: Use a custom key for each zram object Sebastian Andrzej Siewior
2026-07-24 3:24 ` Sergey Senozhatsky
2026-07-24 7:52 ` Sergey Senozhatsky [this message]
2026-07-24 3:26 ` [PATCH 0/2] zram: lockmap tweaks Sergey Senozhatsky
2026-07-24 3:31 ` Sergey Senozhatsky
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=amMY79An64SSBWD4@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@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