qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Francisco Iglesias <frasse.iglesias@gmail.com>,
	Jason Wang <jasowang@redhat.com>
Subject: [PULL V2 16/17] net/dump: Avoid variable length array
Date: Mon, 18 Sep 2023 16:31:31 +0800	[thread overview]
Message-ID: <20230918083132.55423-17-jasowang@redhat.com> (raw)
In-Reply-To: <20230918083132.55423-1-jasowang@redhat.com>

From: Peter Maydell <peter.maydell@linaro.org>

Use a g_autofree heap allocation instead of a variable length
array in dump_receive_iov().

The codebase has very few VLAs, and if we can get rid of them all we
can make the compiler error on new additions.  This is a defensive
measure against security bugs where an on-stack dynamic allocation
isn't correctly size-checked (e.g.  CVE-2021-3527).

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Francisco Iglesias <frasse.iglesias@gmail.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
 net/dump.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net/dump.c b/net/dump.c
index 7d05f16..16073f2 100644
--- a/net/dump.c
+++ b/net/dump.c
@@ -68,7 +68,7 @@ static ssize_t dump_receive_iov(DumpState *s, const struct iovec *iov, int cnt,
     int64_t ts;
     int caplen;
     size_t size = iov_size(iov, cnt) - offset;
-    struct iovec dumpiov[cnt + 1];
+    g_autofree struct iovec *dumpiov = g_new(struct iovec, cnt + 1);
 
     /* Early return in case of previous error. */
     if (s->fd < 0) {
-- 
2.7.4



  parent reply	other threads:[~2023-09-18  8:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  8:31 [PULL V2 00/17] Net patches Jason Wang
2023-09-18  8:31 ` [PULL V2 01/17] tap: Add USO support to tap device Jason Wang
2023-09-18  8:31 ` [PULL V2 02/17] tap: Add check for USO features Jason Wang
2023-09-18  8:31 ` [PULL V2 03/17] virtio-net: Add USO flags to vhost support Jason Wang
2023-09-18  8:31 ` [PULL V2 04/17] virtio-net: Add support for USO features Jason Wang
2023-09-18  8:31 ` [PULL V2 05/17] igb: remove TCP ACK detection Jason Wang
2023-09-18  8:31 ` [PULL V2 06/17] igb: rename E1000E_RingInfo_st Jason Wang
2023-09-18  8:31 ` [PULL V2 07/17] igb: RX descriptors guest writting refactoring Jason Wang
2023-09-18  8:31 ` [PULL V2 08/17] igb: RX payload " Jason Wang
2023-09-18  8:31 ` [PULL V2 09/17] igb: add IPv6 extended headers traffic detection Jason Wang
2023-09-18  8:31 ` [PULL V2 10/17] igb: packet-split descriptors support Jason Wang
2023-09-18  8:31 ` [PULL V2 11/17] e1000e: rename e1000e_ba_state and e1000e_write_hdr_to_rx_buffers Jason Wang
2023-09-18  8:31 ` [PULL V2 12/17] tests: bump libvirt-ci for libasan and libxdp Jason Wang
2023-09-18  8:31 ` [PULL V2 13/17] net: add initial support for AF_XDP network backend Jason Wang
2023-09-18  8:31 ` [PULL V2 14/17] hw/net/fsl_etsec/rings.c: Avoid variable length array Jason Wang
2023-09-18  8:31 ` [PULL V2 15/17] hw/net/rocker: " Jason Wang
2023-09-18  8:31 ` Jason Wang [this message]
2023-09-18  8:31 ` [PULL V2 17/17] net/tap: Avoid variable-length array Jason Wang
2023-09-19 19:12 ` [PULL V2 00/17] Net patches Stefan Hajnoczi

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=20230918083132.55423-17-jasowang@redhat.com \
    --to=jasowang@redhat.com \
    --cc=frasse.iglesias@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).