From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH] unit: correct memcpy overrun in test-dpp
Date: Thu, 26 Oct 2023 09:33:08 -0500 [thread overview]
Message-ID: <ca49a6ae-c9e3-43ac-b99e-dd84cb3caa4a@gmail.com> (raw)
In-Reply-To: <20231025224224.321013-1-prestwoj@gmail.com>
Hi James,
On 10/25/23 17:42, James Prestwood wrote:
> The memcpy in HEX2BUF was copying the length of the buffer that was
> passed in, not the actual length of the converted hexstring. This
> test was segfaulting in the Alpine CI which uses clang/musl.
> ---
> unit/test-dpp.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
Applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2023-10-26 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 22:42 [PATCH] unit: correct memcpy overrun in test-dpp James Prestwood
2023-10-26 14:33 ` Denis Kenzior [this message]
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=ca49a6ae-c9e3-43ac-b99e-dd84cb3caa4a@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).