From: Ying Xue <ying.xue@windriver.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
<jon.maloy@ericsson.com>, <davem@davemloft.net>,
<niveditas98@gmail.com>
Cc: <netdev@vger.kernel.org>, <tipc-discussion@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tipc: Avoid copying bytes beyond the supplied data
Date: Wed, 22 May 2019 15:47:46 +0800 [thread overview]
Message-ID: <2830aab3-3fa9-36d2-5646-d5e4672ae263@windriver.com> (raw)
In-Reply-To: <20190520034536.22782-1-chris.packham@alliedtelesis.co.nz>
On 5/20/19 11:45 AM, Chris Packham wrote:
> TLV_SET is called with a data pointer and a len parameter that tells us
> how many bytes are pointed to by data. When invoking memcpy() we need
> to careful to only copy len bytes.
>
> Previously we would copy TLV_LENGTH(len) bytes which would copy an extra
> 4 bytes past the end of the data pointer which newer GCC versions
> complain about.
>
> In file included from test.c:17:
> In function 'TLV_SET',
> inlined from 'test' at test.c:186:5:
> /usr/include/linux/tipc_config.h:317:3:
> warning: 'memcpy' forming offset [33, 36] is out of the bounds [0, 32]
> of object 'bearer_name' with type 'char[32]' [-Warray-bounds]
> memcpy(TLV_DATA(tlv_ptr), data, tlv_len);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> test.c: In function 'test':
> test.c::161:10: note:
> 'bearer_name' declared here
> char bearer_name[TIPC_MAX_BEARER_NAME];
> ^~~~~~~~~~~
>
> We still want to ensure any padding bytes at the end are initialised, do
> this with a explicit memset() rather than copy bytes past the end of
> data. Apply the same logic to TCM_SET.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Acked-by: Ying Xue <ying.xue@windriver.com>
But please make the same changes in usr/include/linux/tipc_config.h
> ---
>
> Changes in v2:
> - Ensure padding bytes are initialised in both TLV_SET and TCM_SET
>
> include/uapi/linux/tipc_config.h | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/include/uapi/linux/tipc_config.h b/include/uapi/linux/tipc_config.h
> index 4b2c93b1934c..4955e1a9f1bc 100644
> --- a/include/uapi/linux/tipc_config.h
> +++ b/include/uapi/linux/tipc_config.h
> @@ -307,8 +307,10 @@ static inline int TLV_SET(void *tlv, __u16 type, void *data, __u16 len)
> tlv_ptr = (struct tlv_desc *)tlv;
> tlv_ptr->tlv_type = htons(type);
> tlv_ptr->tlv_len = htons(tlv_len);
> - if (len && data)
> - memcpy(TLV_DATA(tlv_ptr), data, tlv_len);
> + if (len && data) {
> + memcpy(TLV_DATA(tlv_ptr), data, len);
> + memset(TLV_DATA(tlv_ptr) + len, 0, TLV_SPACE(len) - tlv_len);
> + }
> return TLV_SPACE(len);
> }
>
> @@ -405,8 +407,10 @@ static inline int TCM_SET(void *msg, __u16 cmd, __u16 flags,
> tcm_hdr->tcm_len = htonl(msg_len);
> tcm_hdr->tcm_type = htons(cmd);
> tcm_hdr->tcm_flags = htons(flags);
> - if (data_len && data)
> + if (data_len && data) {
> memcpy(TCM_DATA(msg), data, data_len);
> + memset(TCM_DATA(msg) + data_len, 0, TCM_SPACE(data_len) - msg_len);
> + }
> return TCM_SPACE(data_len);
> }
>
>
next prev parent reply other threads:[~2019-05-22 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 3:45 Chris Packham
2019-05-22 7:47 ` Ying Xue [this message]
2019-05-22 20:46 ` Chris Packham
2019-05-23 10:20 ` Ying Xue
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=2830aab3-3fa9-36d2-5646-d5e4672ae263@windriver.com \
--to=ying.xue@windriver.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niveditas98@gmail.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®