Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 9 Jul 2021 14:48:46 +0800
From:   Herbert Xu <herbert@gondor.apana.org.au>
To:     Steve French <smfrench@gmail.com>
Cc:     LKML <linux-kernel@vger.kernel.org>,
        James Morris <james.morris@microsoft.com>
Subject: Re: how to request crypto_alloc_shash for GMAC
Message-ID: <20210709064846.GB5907@gondor.apana.org.au>
References: <CAH2r5muOdHbLDQr_p15U0572qF+6MjPK+32JYAf4LUKPuvkLGA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAH2r5muOdHbLDQr_p15U0572qF+6MjPK+32JYAf4LUKPuvkLGA@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Fri, Jul 09, 2021 at 12:48:00AM -0500, Steve French wrote:
>
> Presumably due to https://www.ietf.org/rfc/rfc4543.txt it is already
> supported in the kernel ... but what is the name that it is exposed as
> in the kernel crypto libraries?

We don't have standalone gmac in the kernel, it only exists as
part of the AEAD algorithm gcm.  You're more than welcome to add
it of course.

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt