All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: haoqin huang <haoqinhuang7@gmail.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	 Minchan Kim <minchan@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Nick Terrell <terrelln@fb.com>,  David Sterba <dsterba@suse.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	 Haoqin Huang <haoqinhuang@tencent.com>,
	Rongwei Wang <zigiwang@tencent.com>
Subject: Re: [PATCH v5 3/4] zram: validate parameters in each backend's setup_params
Date: Tue, 4 Aug 2026 17:30:27 +0900	[thread overview]
Message-ID: <anGiqbjPIXg7sUIk@google.com> (raw)
In-Reply-To: <CAEjiKSnECdUd9oZNbhJLiD5NTpOY+fx=mKNnccCXtBLyEC7KCQ@mail.gmail.com>

On (26/08/04 15:02), haoqin huang wrote:
> On Tue, Aug 4, 2026 at 1:37 PM Sergey Senozhatsky
> <senozhatsky@chromium.org> wrote:
> >
> > On (26/08/03 22:12), Haoqin Huang wrote:
> > >  static int deflate_setup_params(struct zcomp_params *params)
> > >  {
> > > +     if (params->dict_sz) {
> > > +             pr_err("deflate: dictionary is not supported\n");
> > > +             return -EOPNOTSUPP;
> > > +     }
> > > +
> > >       if (params->level == ZCOMP_PARAM_NOT_SET)
> > >               params->level = Z_DEFAULT_COMPRESSION;
> >
> > If we want to be pedantic, then {} should also be added to the "if"
> > in this case.  And in other similar cases.
> >
> 
> Okay, thanks for the reminder. I will add {} to the if-branch for consistency.

Thanks.

> > > +     else if (params->level < Z_DEFAULT_COMPRESSION ||
> > > +              params->level > Z_BEST_COMPRESSION) {
> > > +             pr_err("deflate: invalid compression level %d\n", params->level);
> > > +             return -EINVAL;
> > > +     }
> > > +
> >
> > [..]
> > > +     else if (params->level < 1 || params->level > LZ4HC_MAX_CLEVEL) {
> > > +             pr_err("lz4hc: invalid compression level %d\n", params->level);
> > > +             return -EINVAL;
> > > +     }
> >
> > Let's add a small comment justifying/explaining that "1" constant?
> 
> For the lz4hc comment, how about:
>         /*
>          * LZ4HC_compress_generic() clamps levels below 1 to
>          * LZ4HC_DEFAULT_CLEVEL, so < 1 is the real lower bound.
>          */
> Does that look reasonable?

I suppose we want to document the fact that LZ4HC_MIN_CLEVEL (which
would be naturally expected here) is set to 3 and cuts off levels 1
and 2 which are perfectly valid.  Maybe just say something like that,
for simplicity.

  reply	other threads:[~2026-08-04  8:30 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27  7:02 [PATCH 1/3] zram: fix zstd dict use-after-free on per-CPU error path Haoqin Huang
2026-06-27  7:02 ` [PATCH 2/3] zram: add per-backend capability flags and validate parameters early Haoqin Huang
2026-07-24  5:27   ` Sergey Senozhatsky
2026-07-27 16:50     ` haoqin huang
2026-07-28  1:19       ` Sergey Senozhatsky
2026-07-28  9:07         ` haoqin huang
2026-07-28  1:27   ` Sergey Senozhatsky
2026-07-28  9:09     ` haoqin huang
2026-06-27  7:02 ` [PATCH 3/3] zram: reset per-priority params when changing algorithm before init Haoqin Huang
2026-07-24  5:19   ` Sergey Senozhatsky
2026-07-07  7:19 ` [PATCH 1/3] zram: fix zstd dict use-after-free on per-CPU error path Sergey Senozhatsky
2026-07-24  5:17 ` Sergey Senozhatsky
2026-07-27 16:06   ` haoqin huang
2026-07-28  1:21     ` Sergey Senozhatsky
2026-07-28  9:29 ` [PATCH v2 1/5] zram: fix early release of global cdict/ddict in " Haoqin Huang
2026-07-28  9:29   ` [PATCH v2 2/5] zram: make dict update in comp_params_store() atomic Haoqin Huang
2026-07-29  2:30     ` Sergey Senozhatsky
2026-07-29  4:06       ` haoqin huang
2026-07-29  4:16         ` Sergey Senozhatsky
2026-07-29  4:25           ` haoqin huang
2026-07-28  9:29   ` [PATCH v2 3/5] zstd: move ZSTD_MAX_CLEVEL to zstd_lib.h Haoqin Huang
2026-07-29  3:03     ` Sergey Senozhatsky
2026-07-29  4:16       ` haoqin huang
2026-07-29  4:22         ` Sergey Senozhatsky
2026-07-29  4:32           ` haoqin huang
2026-07-29  4:49             ` Sergey Senozhatsky
2026-07-30  2:48               ` haoqin huang
2026-07-28  9:29   ` [PATCH v2 4/5] zram: add per-backend caps and validate parameters early Haoqin Huang
2026-07-29  2:26     ` Sergey Senozhatsky
2026-07-29  3:53       ` haoqin huang
2026-07-28  9:29   ` [PATCH v2 5/5] zram: reset per-priority params when changing algorithm before init Haoqin Huang
2026-07-29  0:34   ` [PATCH v2 1/5] zram: fix early release of global cdict/ddict in per-CPU error path Andrew Morton
2026-07-29  2:49     ` Sergey Senozhatsky
2026-07-29  3:33     ` haoqin huang
2026-07-29  2:20   ` Sergey Senozhatsky
2026-07-29  3:40     ` haoqin huang
2026-07-29  2:40   ` Sergey Senozhatsky
2026-07-30  2:52   ` [PATCH v3 0/5] zram: fix zstd per-CPU error path and add parameter validation Haoqin Huang
2026-07-30  2:52     ` [PATCH v3 1/5] zram: do not release zstd params in per-CPU error path Haoqin Huang
2026-07-30  2:52     ` [PATCH v3 2/5] zram: reject zero-size dictionary Haoqin Huang
2026-07-30  2:52     ` [PATCH v3 3/5] zram: add level validation in zstd setup_params Haoqin Huang
2026-07-30  3:10       ` Sergey Senozhatsky
2026-07-30  5:55         ` haoqin huang
2026-07-30  2:52     ` [PATCH v3 4/5] zram: add per-backend caps and validate parameters early Haoqin Huang
2026-07-30  3:14       ` Sergey Senozhatsky
2026-07-30  5:57         ` haoqin huang
2026-07-30  2:52     ` [PATCH v3 5/5] zram: reset per-priority params when changing algorithm before init Haoqin Huang
2026-07-30  6:01     ` [PATCH v4 0/4] zram: fix zstd per-CPU error path and add parameter validation Haoqin Huang
2026-07-30  6:01       ` [PATCH v4 1/4] zram: do not release zstd params in per-CPU error path Haoqin Huang
2026-07-30  6:01       ` [PATCH v4 2/4] zram: reject zero-size dictionary Haoqin Huang
2026-07-30  7:00         ` Sergey Senozhatsky
2026-07-30  6:01       ` [PATCH v4 3/4] zram: validate parameters in each backend's setup_params Haoqin Huang
2026-07-30  7:24         ` Sergey Senozhatsky
2026-08-03 12:20           ` haoqin huang
2026-08-04  4:42             ` Sergey Senozhatsky
2026-08-04  4:42               ` [f2fs-dev] " Sergey Senozhatsky
2026-08-05  1:26               ` Jaegeuk Kim via Linux-f2fs-devel
2026-08-05  1:26                 ` Jaegeuk Kim
2026-07-30  7:35         ` Sergey Senozhatsky
2026-07-30  6:01       ` [PATCH v4 4/4] zram: reset per-priority params when changing algorithm before init Haoqin Huang
2026-07-30  7:28         ` Sergey Senozhatsky
2026-08-03 14:12       ` [PATCH v5 0/4] zram: fix zstd error paths and add parameter validation Haoqin Huang
2026-08-03 14:12         ` [PATCH v5 1/4] zram: do not release zstd global params from error paths Haoqin Huang
2026-08-03 14:12         ` [PATCH v5 2/4] zram: reject zero-size dictionary Haoqin Huang
2026-08-04  5:32           ` Sergey Senozhatsky
2026-08-04  7:15             ` haoqin huang
2026-08-03 14:12         ` [PATCH v5 3/4] zram: validate parameters in each backend's setup_params Haoqin Huang
2026-08-04  5:36           ` Sergey Senozhatsky
2026-08-04  7:02             ` haoqin huang
2026-08-04  8:30               ` Sergey Senozhatsky [this message]
2026-08-04  5:48           ` Sergey Senozhatsky
2026-08-04  7:13             ` haoqin huang
2026-08-04  8:28               ` Sergey Senozhatsky
2026-08-03 14:12         ` [PATCH v5 4/4] zram: reset per-priority params when changing algorithm before init Haoqin Huang
2026-08-04  9:38         ` [PATCH v6 0/5] zram: fix zstd error paths and add parameter validation Haoqin Huang
2026-08-04  9:38           ` [PATCH v6 1/5] zram: do not release zstd global params from error paths Haoqin Huang
2026-08-04  9:38           ` [PATCH v6 2/5] zram: reject zero-size dictionary Haoqin Huang
2026-08-04  9:38           ` [PATCH v6 3/5] zram: add pr_fmt to backend files Haoqin Huang
2026-08-04  9:38           ` [PATCH v6 4/5] zram: validate parameters in each backend's setup_params Haoqin Huang
2026-08-04  9:38           ` [PATCH v6 5/5] zram: reset per-priority params when changing algorithm before init Haoqin Huang
2026-08-04  9:53           ` [PATCH v6 0/5] zram: fix zstd error paths and add parameter validation Sergey Senozhatsky
2026-08-04  9:55             ` Sergey Senozhatsky
2026-08-04 19:55           ` Andrew Morton

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=anGiqbjPIXg7sUIk@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=dsterba@suse.com \
    --cc=haoqinhuang7@gmail.com \
    --cc=haoqinhuang@tencent.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=terrelln@fb.com \
    --cc=zigiwang@tencent.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.