All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5 04/23] zram: introduce custom comp backends API
Date: Sun, 7 Jul 2024 10:31:51 +0900	[thread overview]
Message-ID: <20240707013151.GB244190@google.com> (raw)
In-Reply-To: <8fe873d4-b9c4-47ad-b779-e1012677011e@t-8ch.de>

On (24/07/06 09:50), Thomas Weißschuh wrote:
> >  /* dynamic per-device compression frontend */
> >  struct zcomp {
> >  	struct zcomp_strm __percpu *stream;
> > -	const char *name;
> > +	struct zcomp_ops *ops;
>
> If this is "const struct zcomp_ops *ops" then all the backend struct
> zcomp_ops definitions could be constified, improving security.

I guess I can do that.

  reply	other threads:[~2024-07-07  1:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06  4:56 [PATCHv5 00/23] zram: compression algorithms tunables Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 01/23] lib: zstd: export API needed for dictionary support Sergey Senozhatsky
2024-07-06  8:20   ` [PATCH v5 " Markus Elfring
2024-07-06  4:56 ` [PATCHv5 02/23] lib: lz4hc: export LZ4_resetStreamHC symbol Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 03/23] lib: zstd: fix null-deref in ZSTD_createCDict_advanced2() Sergey Senozhatsky
2024-07-06  7:20   ` [PATCH v5 " Markus Elfring
2024-07-06  4:56 ` [PATCHv5 04/23] zram: introduce custom comp backends API Sergey Senozhatsky
2024-07-06  7:50   ` Thomas Weißschuh
2024-07-07  1:31     ` Sergey Senozhatsky [this message]
2024-07-06  4:56 ` [PATCHv5 05/23] zram: add lzo and lzorle compression backends support Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 06/23] zram: add lz4 compression backend support Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 07/23] zram: add lz4hc " Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 08/23] zram: add zstd " Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 09/23] zram: pass estimated src size hint to zstd Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 10/23] zram: add zlib compression backend support Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 11/23] zram: add 842 " Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 12/23] zram: check that backends array has at least one backend Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 13/23] zram: introduce zcomp_params structure Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 14/23] zram: recalculate zstd compression params once Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 15/23] zram: extend comp_algorithm attr write handling Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 16/23] zram: add support for dict comp config Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 17/23] zram: introduce zcomp_req structure Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 18/23] zram: introduce zcomp_ctx structure Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 19/23] zram: move immutable comp params away from per-CPU context Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 20/23] zram: add dictionary support to lz4 Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 21/23] zram: add dictionary support to lz4hc Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 22/23] zram: add dictionary support to zstd backend Sergey Senozhatsky
2024-07-06  4:56 ` [PATCHv5 23/23] Documentation/zram: add documentation for algorithm parameters Sergey Senozhatsky
2024-07-06  5:01 ` [PATCHv5 00/23] zram: compression algorithms tunables Sergey Senozhatsky
2024-07-06  7:03 ` Markus Elfring

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=20240707013151.GB244190@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --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 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.