[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240515050705.GF950946@google.com>
Date: Wed, 15 May 2024 14:07:05 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: kernel test robot <lkp@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan@...nel.org>, llvm@...ts.linux.dev,
oe-kbuild-all@...ts.linux.dev,
Linux Memory Management List <linux-mm@...ck.org>,
linux-kernel@...r.kernel.org,
"linux-block@...r.kernel.org Nick Terrell" <terrelln@...com>
Subject: Re: [PATCHv3 02/19] zram: add lzo and lzorle compression backends
support
On (24/05/10 14:33), Sergey Senozhatsky wrote:
> On (24/05/09 19:23), kernel test robot wrote:
> > config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240509/202405091921.320BxOyE-lkp@intel.com/config)
> [..]
> > >> ERROR: modpost: "backend_lzorle" [drivers/block/zram/zram.ko] undefined!
> > >> ERROR: modpost: "backend_lzo" [drivers/block/zram/zram.ko] undefined!
>
> ... and that's how learned that my .config has ZRAM=y
This has revealed several problems. First, lz4hc misses one symbol
export, an easy fix. Second, zstd misses pretty much all of the
advanced c/d dict, c/d ctx API that we need in order to use dicts
in a module. I have fixes for both in v4 on this series (I'll Cc
Nick on lz4/zstd patches). I think I'll just send out v4 today, simply
because there are patches there that we can re-use even if we scratch
zram backends and continue using crypto API.
Powered by blists - more mailing lists