From: Bart Van Assche <bvanassche@acm.org>
To: Hangyu Hua <hbh25y@gmail.com>,
jgg@ziepe.ca, leon@kernel.org, gustavoars@kernel.org
Cc: linux-rdma@vger.kernel.org, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] infiniband: ulp: srpt: Use flex array destination for memcpy()
Date: Fri, 9 Sep 2022 09:13:44 -0700 [thread overview]
Message-ID: <253db188-04d2-6bea-4d4f-33371bfae929@acm.org> (raw)
In-Reply-To: <20220909022943.8896-1-hbh25y@gmail.com>
On 9/8/22 19:29, Hangyu Hua wrote:
> In preparation for FORTIFY_SOURCE performing run-time destination buffer
> bounds checking for memcpy(), specify the destination output buffer
> explicitly, instead of asking memcpy() to write past the end of what looked
> like a fixed-size object.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2022-09-09 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 2:29 [PATCH] infiniband: ulp: srpt: Use flex array destination for memcpy() Hangyu Hua
2022-09-09 9:40 ` Gustavo A. R. Silva
2022-09-09 16:13 ` Bart Van Assche [this message]
2022-09-20 12:11 ` Leon Romanovsky
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=253db188-04d2-6bea-4d4f-33371bfae929@acm.org \
--to=bvanassche@acm.org \
--cc=gustavoars@kernel.org \
--cc=hbh25y@gmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=target-devel@vger.kernel.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