[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02dd5000-7ced-df02-d9d0-a3c1a410d062@huawei.com>
Date: Sat, 15 Mar 2025 13:15:09 +0800
From: Zhihao Cheng <chengzhihao1@...wei.com>
To: Herbert Xu <herbert@...dor.apana.org.au>, Linux Crypto Mailing List
<linux-crypto@...r.kernel.org>
CC: Richard Weinberger <richard@....at>, <linux-mtd@...ts.infradead.org>,
"Rafael J. Wysocki" <rafael@...nel.org>, Pavel Machek <pavel@....cz>,
<linux-pm@...r.kernel.org>, Steffen Klassert <steffen.klassert@...unet.com>,
<netdev@...r.kernel.org>
Subject: Re: [v4 PATCH 10/13] ubifs: Use crypto_acomp interface
在 2025/3/14 20:22, Herbert Xu 写道:
> Replace the legacy crypto compression interface with the new acomp
> interface.
>
> Remove the compression mutexes and the overallocation for memory
> (the offender LZO has been fixed).
Hi, Herbert. Can you show me which patch fixed the problem in LZO?
>
> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>
> ---
> fs/ubifs/compress.c | 116 ++++++++++++++++++++++++++++----------------
> fs/ubifs/journal.c | 2 +-
> fs/ubifs/ubifs.h | 15 +-----
> 3 files changed, 77 insertions(+), 56 deletions(-)
>
[...]
> diff --git a/fs/ubifs/ubifs.h b/fs/ubifs/ubifs.h
> index 3375bbe0508c..7d0aaf5d2e23 100644
> --- a/fs/ubifs/ubifs.h
> +++ b/fs/ubifs/ubifs.h
> @@ -124,13 +124,6 @@
> #define OLD_ZNODE_AGE 20
> #define YOUNG_ZNODE_AGE 5
>
> -/*
> - * Some compressors, like LZO, may end up with more data then the input buffer.
> - * So UBIFS always allocates larger output buffer, to be sure the compressor
> - * will not corrupt memory in case of worst case compression.
> - */
> -#define WORST_COMPR_FACTOR 2
Does LZO guarantee the output data length smaller than input buffer
length? Which commit fixed the issue?
> -
> #ifdef CONFIG_FS_ENCRYPTION
> #define UBIFS_CIPHER_BLOCK_SIZE FSCRYPT_CONTENTS_ALIGNMENT
> #else
Powered by blists - more mailing lists