From: Nick Terrell <nickrterrell@gmail.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: squashfs-devel@lists.sourceforge.net,
Chris Mason <chris.mason@fusionio.com>,
kbuild-all@lists.01.org, kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Petr Malat <oss@malat.biz>,
linux-crypto@vger.kernel.org, Kernel Team <Kernel-team@fb.com>,
linux-btrfs@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [f2fs-dev] [PATCH v8 1/3] lib: zstd: Add kernel-specific API
Date: Sun, 28 Mar 2021 13:27:08 -0700 [thread overview]
Message-ID: <CANr2DbeAXeYRMAa1UjP5kNqniWQvt2nM93ZjmWioEuR4qZxf1g@mail.gmail.com> (raw)
In-Reply-To: <20210327214810.ldijpbr2tnkh2gce@spock.localdomain>
On Sat, Mar 27, 2021 at 2:48 PM Oleksandr Natalenko
<oleksandr@natalenko.name> wrote:
>
> Hello.
>
> On Sat, Mar 27, 2021 at 05:48:01PM +0800, kernel test robot wrote:
> > >> ERROR: modpost: "ZSTD_maxCLevel" [fs/f2fs/f2fs.ko] undefined!
>
> Since f2fs can be built as a module, the following correction seems to
> be needed:
Thanks Oleksandr! Looks like f2fs has been updated to use
ZSTD_maxCLevel() since the first version of these patches. I'll put up
a new version shortly with the fix, and update my test suite to build
f2fs and other users as modules, so it can catch this.
Best,
Nick
> ```
> diff --git a/lib/zstd/compress/zstd_compress.c b/lib/zstd/compress/zstd_compress.c
> index 9c998052a0e5..584c92c51169 100644
> --- a/lib/zstd/compress/zstd_compress.c
> +++ b/lib/zstd/compress/zstd_compress.c
> @@ -4860,6 +4860,7 @@ size_t ZSTD_endStream(ZSTD_CStream* zcs, ZSTD_outBuffer* output)
>
> #define ZSTD_MAX_CLEVEL 22
> int ZSTD_maxCLevel(void) { return ZSTD_MAX_CLEVEL; }
> +EXPORT_SYMBOL(ZSTD_maxCLevel);
> int ZSTD_minCLevel(void) { return (int)-ZSTD_TARGETLENGTH_MAX; }
>
> static const ZSTD_compressionParameters ZSTD_defaultCParameters[4][ZSTD_MAX_CLEVEL+1] = {
> ```
>
> Not sure if the same should be done for `ZSTD_minCLevel()` since I don't
> see it being used anywhere else.
>
> --
> Oleksandr Natalenko (post-factum)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-03-28 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 19:18 [f2fs-dev] [PATCH v8 0/3] Update to zstd-1.4.10 Nick Terrell
2021-03-26 19:18 ` [f2fs-dev] [PATCH v8 1/3] lib: zstd: Add kernel-specific API Nick Terrell
[not found] ` <202103271719.VoxPHugN-lkp@intel.com>
2021-03-27 21:48 ` Oleksandr Natalenko via Linux-f2fs-devel
2021-03-28 20:27 ` Nick Terrell [this message]
2021-03-26 19:18 ` [f2fs-dev] [PATCH v8 2/3] lib: zstd: Add decompress_sources.h for decompress_unzstd Nick Terrell
2021-03-26 19:18 ` [f2fs-dev] [PATCH v8 3/3] lib: zstd: Upgrade to latest upstream zstd version 1.4.10 Nick Terrell
[not found] ` <202103270534.OKizLwFF-lkp@intel.com>
2021-03-26 23:47 ` Nick Terrell
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=CANr2DbeAXeYRMAa1UjP5kNqniWQvt2nM93ZjmWioEuR4qZxf1g@mail.gmail.com \
--to=nickrterrell@gmail.com \
--cc=Kernel-team@fb.com \
--cc=chris.mason@fusionio.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oleksandr@natalenko.name \
--cc=oss@malat.biz \
--cc=squashfs-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).