From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Move SHA2 routines to a new generic API layer for crypto hashes |
Date: | 2020-12-02 02:42:58 |
Message-ID: | cee3df00-566a-400c-1252-67c3701f918a@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 2020/12/02 10:41, Michael Paquier wrote:
> Move SHA2 routines to a new generic API layer for crypto hashes
Thanks for improving this!
I got the following compiler failure. ISTM that the variable "status"
in both pg_cryptohash_update() and pg_cryptohash_final() needs
to be initialized with 0. Patch attached. Thought?
cryptohash_openssl.c: In function ‘pg_cryptohash_update’:
cryptohash_openssl.c:144:5: error: ‘status’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (status <= 0)
^
cryptohash_openssl.c: In function ‘pg_cryptohash_final’:
cryptohash_openssl.c:179:5: error: ‘status’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (status <= 0)
^
cc1: all warnings being treated as errors
make[2]: *** [cryptohash_openssl.o] Error 1
<builtin>: recipe for target 'cryptohash_openssl.o' failed
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Attachment | Content-Type | Size |
---|---|---|
initialize_status.patch | text/plain | 641 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-12-02 03:14:33 | Re: pgsql: Move SHA2 routines to a new generic API layer for crypto hashes |
Previous Message | Fujii Masao | 2020-12-02 02:00:55 | pgsql: Allow restore_command parameter to be changed with reload. |