From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH] crypto: fix copy size causing overruns/crashing
Date: Thu, 03 Oct 2019 11:53:21 -0500 [thread overview]
Message-ID: <067fa11c-3de1-e893-02d7-526d2ab2efb5@gmail.com> (raw)
In-Reply-To: <20191003113516.GC8802@dtznix>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi Will,
On 10/3/19 11:35 AM, Will Dietz wrote:
> num_ad is already accounted for in `sizeof(iov)`
> as iov has size `sizeof(struct iovec) * (num_ad+1)`.
> ---
> src/crypto.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Can you use git send-email to submit this? When I save this message it
comes in as multipart with the signature, etc included and seems to
confuse git am.
Regards,
-Denis
next prev parent reply other threads:[~2019-10-03 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 16:35 [PATCH] crypto: fix copy size causing overruns/crashing Will Dietz
2019-10-03 16:44 ` Prestwood, James
2019-10-03 16:47 ` Prestwood, James
2019-10-03 16:47 ` Denis Kenzior
2019-10-03 16:53 ` Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-03 17:18 Will Dietz
2019-10-03 17:28 ` Denis Kenzior
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=067fa11c-3de1-e893-02d7-526d2ab2efb5@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.org \
/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