[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250911184705.GD1376@sol>
Date: Thu, 11 Sep 2025 11:47:05 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Guan-Chun Wu <409411716@....tku.edu.tw>
Cc: akpm@...ux-foundation.org, axboe@...nel.dk, ceph-devel@...r.kernel.org,
hch@....de, home7438072@...il.com, idryomov@...il.com,
jaegeuk@...nel.org, kbusch@...nel.org,
linux-fscrypt@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, sagi@...mberg.me, tytso@....edu,
visitorckw@...il.com, xiubli@...hat.com
Subject: Re: [PATCH v2 4/5] fscrypt: replace local base64url helpers with
generic lib/base64 helpers
On Thu, Sep 11, 2025 at 03:45:56PM +0800, Guan-Chun Wu wrote:
> Replace the existing local base64url encoding and decoding functions in
> fscrypt with the generic base64_encode_custom and base64_decode_custom
> helpers from the kernel's lib/base64 library.
But those aren't the functions that are actually used.
> This removes custom implementations in fscrypt, reduces code duplication,
> and leverages the well-maintained,
Who is maintaining lib/base64.c? I guess Andrew?
> standard base64 code within the kernel.
fscrypt uses "base64url", not "base64".
> /* Encoded size of max-size no-key name */
> #define FSCRYPT_NOKEY_NAME_MAX_ENCODED \
> - FSCRYPT_BASE64URL_CHARS(FSCRYPT_NOKEY_NAME_MAX)
> + BASE64_CHARS(FSCRYPT_NOKEY_NAME_MAX)
Does BASE64_CHARS() include '=' padding or not?
- Eric
Powered by blists - more mailing lists