linux-kernel - Re: [PATCHv5 04/23] zram: introduce custom comp backends API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240707013151.GB244190@google.com>
Date: Sun, 7 Jul 2024 10:31:51 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Minchan Kim <minchan@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv5 04/23] zram: introduce custom comp backends API

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.