[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKhP6FFYF0O=Vy6aMqJxD9Ubt80nX9Mh=guU8wgUzvzQw@mail.gmail.com>
Date: Wed, 1 Aug 2018 15:38:07 -0700
From: Kees Cook <keescook@...omium.org>
To: Geliang Tang <geliangtang@...il.com>
Cc: Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pstore: add zstd compression support
On Wed, Aug 1, 2018 at 4:23 AM, Geliang Tang <geliangtang@...il.com> wrote:
> This patch added the 6th compression algorithm support for pstore: zstd.
>
> Signed-off-by: Geliang Tang <geliangtang@...il.com>
Thanks! I've applied this to my tree and it should be visible in -next soon.
> +#if IS_ENABLED(CONFIG_PSTORE_ZSTD_COMPRESS)
> +static int zbufsize_zstd(size_t size)
> +{
> + return ZSTD_compressBound(size);
> +}
> +#endif
One thing I've been pondering is if there might be a way to extend the
crypto compression API to provide the "buffer output size" interface
directly. If that happened, pstore wouldn't need per-compression-algo
entries like it still has.
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists