From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH 4/4] unit: add unit test for DPP crypto operations
Date: Mon, 06 Dec 2021 16:37:43 -0600 [thread overview]
Message-ID: <12a63363-93db-46db-813a-b9f91353d86e@gmail.com> (raw)
In-Reply-To: 20211206210356.1204046-4-prestwoj@gmail.com
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
Hi James,
On 12/6/21 3:03 PM, James Prestwood wrote:
> ---
> Makefile.am | 7 ++-
> unit/test-dpp.c | 147 ++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 153 insertions(+), 1 deletion(-)
> create mode 100644 unit/test-dpp.c
>
<snip>
> @@ -547,6 +548,10 @@ unit_test_p2p_SOURCES = unit/test-p2p.c src/wscutil.h src/wscutil.c \
> src/band.h src/band.c
> unit_test_p2p_LDADD = $(ell_ldadd)
>
> +unit_test_dpp_SOURCES = unit/test-dpp.c src/dpp-util.h src/dpp-util.c \
> + src/util.h src/util.c src/crypto.h src/crypto.c
I had to add src/band.[ch] here
> +unit_test_dpp_LDADD = $(ell_ldadd)
> +
> TESTS = $(unit_tests)
>
> EXTRA_DIST = src/genbuiltin src/iwd.service.in src/net.connman.iwd.service \
<snip>
> +const char *i_proto_public_bytes = "50a532ae2a07207276418d2fa630295d45569be425aa634f02014d00a7d1f61a";
I changed some of these data lines to be 80 char / line compliant.
Applied, but I'm seeing this:
TEST: DPP test key derivation
=================================================================
==17289==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 536 byte(s) in 7 object(s) allocated from:
#0 0x7f88cc96d0f8 in __interceptor_malloc
(/usr/lib/gcc/x86_64-pc-linux-gnu/9.4.0/libasan.so.5+0x10c0f8)
#1 0x4199d2 in l_malloc ell/util.c:62
SUMMARY: AddressSanitizer: 536 byte(s) leaked in 7 allocation(s).
Regards,
-Denis
next reply other threads:[~2021-12-06 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 22:37 Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-06 21:03 [PATCH 4/4] unit: add unit test for DPP crypto operations James Prestwood
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=12a63363-93db-46db-813a-b9f91353d86e@gmail.com \
--to=iwd@lists.linux.dev \
/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