From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,minchan@kernel.org,gaoxu2@honor.com,bgeffon@google.com,axboe@kernel.dk,senozhatsky@chromium.org,akpm@linux-foundation.org
Subject: + zram-unify-and-harden-algo-priority-params-handling.patch added to mm-unstable branch
Date: Wed, 11 Mar 2026 11:12:57 -0700 [thread overview]
Message-ID: <20260311181258.41604C4CEF7@smtp.kernel.org> (raw)
The patch titled
Subject: zram: unify and harden algo/priority params handling
has been added to the -mm mm-unstable branch. Its filename is
zram-unify-and-harden-algo-priority-params-handling.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/zram-unify-and-harden-algo-priority-params-handling.patch
This patch will later appear in the mm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: zram: unify and harden algo/priority params handling
Date: Wed, 11 Mar 2026 17:42:49 +0900
We have two functions that accept algo= and priority= params -
algorithm_params_store() and recompress_store(). This patch unifies and
hardens handling of those parameters.
There are 4 possible cases:
- only priority= provided [recommended]
We need to verify that provided priority value is
within permitted range for each particular function.
- both algo= and priority= provided
We cannot prioritize one over another. All we should
do is to verify that zram is configured in the way
that user-space expects it to be. Namely that zram
indeed has compressor algo= setup at given priority=.
- only algo= provided [not recommended]
We should lookup priority in compressors list.
- none provided [not recommended]
Just use function's defaults.
Link: https://lkml.kernel.org/r/20260311084312.1766036-7-senozhatsky@chromium.org
Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Suggested-by: Minchan Kim <minchan@kernel.org>
Cc: Brian Geffon <bgeffon@google.com>
Cc: gao xu <gaoxu2@honor.com>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/block/zram/zram_drv.c | 106 +++++++++++++++++++-------------
1 file changed, 66 insertions(+), 40 deletions(-)
--- a/drivers/block/zram/zram_drv.c~zram-unify-and-harden-algo-priority-params-handling
+++ a/drivers/block/zram/zram_drv.c
@@ -1635,6 +1635,37 @@ static void zram_debugfs_register(struct
static void zram_debugfs_unregister(struct zram *zram) {};
#endif
+/* Only algo parameter given, lookup by algo name */
+static int lookup_algo_priority(struct zram *zram, const char *algo,
+ u32 min_prio)
+{
+ s32 prio;
+
+ for (prio = min_prio; prio < ZRAM_MAX_COMPS; prio++) {
+ if (!zram->comp_algs[prio])
+ continue;
+
+ if (!strcmp(zram->comp_algs[prio], algo))
+ return prio;
+ }
+
+ return -EINVAL;
+}
+
+/* Both algo and priority parameters given, validate them */
+static int validate_algo_priority(struct zram *zram, const char *algo, u32 prio)
+{
+ if (prio >= ZRAM_MAX_COMPS)
+ return -EINVAL;
+ /* No algo at given priority */
+ if (!zram->comp_algs[prio])
+ return -EINVAL;
+ /* A different algo at given priority */
+ if (strcmp(zram->comp_algs[prio], algo))
+ return -EINVAL;
+ return 0;
+}
+
static void comp_algorithm_set(struct zram *zram, u32 prio, const char *alg)
{
zram->comp_algs[prio] = alg;
@@ -1707,6 +1738,7 @@ static ssize_t algorithm_params_store(st
char *args, *param, *val, *algo = NULL, *dict_path = NULL;
struct deflate_params deflate_params;
struct zram *zram = dev_to_zram(dev);
+ bool prio_param = false;
int ret;
deflate_params.winbits = ZCOMP_PARAM_NOT_SET;
@@ -1719,6 +1751,7 @@ static ssize_t algorithm_params_store(st
return -EINVAL;
if (!strcmp(param, "priority")) {
+ prio_param = true;
ret = kstrtoint(val, 10, &prio);
if (ret)
return ret;
@@ -1754,24 +1787,22 @@ static ssize_t algorithm_params_store(st
if (init_done(zram))
return -EBUSY;
- /* Lookup priority by algorithm name */
- if (algo) {
- s32 p;
-
- prio = -EINVAL;
- for (p = ZRAM_PRIMARY_COMP; p < ZRAM_MAX_COMPS; p++) {
- if (!zram->comp_algs[p])
- continue;
+ if (prio_param) {
+ if (prio < ZRAM_PRIMARY_COMP || prio >= ZRAM_MAX_COMPS)
+ return -EINVAL;
+ }
- if (!strcmp(zram->comp_algs[p], algo)) {
- prio = p;
- break;
- }
- }
+ if (algo && prio_param) {
+ ret = validate_algo_priority(zram, algo, prio);
+ if (ret)
+ return ret;
}
- if (prio < ZRAM_PRIMARY_COMP || prio >= ZRAM_MAX_COMPS)
- return -EINVAL;
+ if (algo && !prio_param) {
+ prio = lookup_algo_priority(zram, algo, ZRAM_PRIMARY_COMP);
+ if (prio < 0)
+ return -EINVAL;
+ }
ret = comp_params_store(zram, prio, level, dict_path, &deflate_params);
return ret ? ret : len;
@@ -2407,9 +2438,6 @@ static int recompress_slot(struct zram *
void *src;
int ret = 0;
- if (!zram->comps[prio])
- return -EINVAL;
-
handle_old = get_slot_handle(zram, index);
if (!handle_old)
return -EINVAL;
@@ -2511,10 +2539,11 @@ static ssize_t recompress_store(struct d
char *args, *param, *val, *algo = NULL;
u64 num_recomp_pages = ULLONG_MAX;
struct zram_pp_ctl *ctl = NULL;
- u32 prio = ZRAM_SECONDARY_COMP;
- struct zram_pp_slot *pps;
+ s32 prio = ZRAM_SECONDARY_COMP;
u32 mode = 0, threshold = 0;
+ struct zram_pp_slot *pps;
struct page *page = NULL;
+ bool prio_param = false;
ssize_t ret;
args = skip_spaces(buf);
@@ -2562,7 +2591,8 @@ static ssize_t recompress_store(struct d
}
if (!strcmp(param, "priority")) {
- ret = kstrtouint(val, 10, &prio);
+ prio_param = true;
+ ret = kstrtoint(val, 10, &prio);
if (ret)
return ret;
continue;
@@ -2576,30 +2606,26 @@ static ssize_t recompress_store(struct d
if (!init_done(zram))
return -EINVAL;
- if (algo) {
- bool found = false;
-
- for (; prio < ZRAM_MAX_COMPS; prio++) {
- if (!zram->comp_algs[prio])
- continue;
-
- if (!strcmp(zram->comp_algs[prio], algo)) {
- found = true;
- break;
- }
- }
+ if (prio_param) {
+ if (prio < ZRAM_SECONDARY_COMP || prio >= ZRAM_MAX_COMPS)
+ return -EINVAL;
+ }
- if (!found) {
- ret = -EINVAL;
- goto out;
- }
+ if (algo && prio_param) {
+ ret = validate_algo_priority(zram, algo, prio);
+ if (ret)
+ return ret;
}
- if (prio < ZRAM_SECONDARY_COMP || prio >= ZRAM_MAX_COMPS) {
- ret = -EINVAL;
- goto out;
+ if (algo && !prio_param) {
+ prio = lookup_algo_priority(zram, algo, ZRAM_SECONDARY_COMP);
+ if (prio < 0)
+ return -EINVAL;
}
+ if (!zram->comps[prio])
+ return -EINVAL;
+
page = alloc_page(GFP_KERNEL);
if (!page) {
ret = -ENOMEM;
_
Patches currently in -mm which might be from senozhatsky@chromium.org are
zram-do-not-permit-params-change-after-init.patch
zram-do-not-autocorrect-bad-recompression-parameters.patch
zram-drop-num_active_comps.patch
zram-update-recompression-documentation.patch
zram-remove-chained-recompression.patch
zram-unify-and-harden-algo-priority-params-handling.patch
reply other threads:[~2026-03-11 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260311181258.41604C4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bgeffon@google.com \
--cc=gaoxu2@honor.com \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=senozhatsky@chromium.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.