From: Alex Williamson <alex@shazbot.org>
To: Alex Mastro <amastro@fb.com>
Cc: David Matlack <dmatlack@google.com>,
Shuah Khan <shuah@kernel.org>,
Raghavendra Rao Ananta <rananta@google.com>,
Vipin Sharma <vipinsh@google.com>, <kvm@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
alex@shazbot.org
Subject: Re: [PATCH v4 0/2] vfio: selftests: Add allocation assert helpers and avoid VLAs
Date: Fri, 17 Jul 2026 09:43:52 -0600 [thread overview]
Message-ID: <20260717094352.6bb38603@shazbot.org> (raw)
In-Reply-To: <20260617-scratch-amastro-vfio-selftests-avoid-vlas-v4-0-b9f52f1e2c5a@fb.com>
On Wed, 17 Jun 2026 11:57:59 -0700
Alex Mastro <amastro@fb.com> wrote:
> Add VFIO selftest {malloc,calloc}_assert() helpers, then use
> them in places that open-code malloc() or calloc() followed by
> VFIO_ASSERT_NOT_NULL().
>
> Use the helpers to replace VLAs with heap allocations. This avoids GCC
> rejecting initialized VLAs and avoids treating a u8 buffer as a possibly
> under-aligned VFIO request struct.
>
> Changes in v4:
> - Add malloc_assert().
> - Link to v3: https://patch.msgid.link/20260615-scratch-amastro-vfio-selftests-avoid-vlas-v3-0-b3798415c72a@fb.com
>
> Changes in v3:
> - Add the calloc_assert() helper as a precursor patch.
> - Convert existing VFIO selftest calloc() assertion sites.
> - Update the VLA fix to use calloc_assert().
> - Link to v2: https://patch.msgid.link/20260615-scratch-amastro-vfio-selftests-avoid-vlas-v2-1-4e4df462908a@fb.com
>
> Changes in v2:
> - Reverse xmas tree variable ordering
> - Link to v1: https://patch.msgid.link/20260612-scratch-amastro-vfio-selftests-avoid-vlas-v1-1-ba3acb635f0a@fb.com
>
> Signed-off-by: Alex Mastro <amastro@fb.com>
> ---
> Alex Mastro (2):
> vfio: selftests: Add allocation assert helpers
> vfio: selftests: Avoid VLAs
>
> .../selftests/vfio/lib/include/libvfio/assert.h | 18 ++++++++++++
> tools/testing/selftests/vfio/lib/iommu.c | 12 +++-----
> tools/testing/selftests/vfio/lib/iova_allocator.c | 4 +--
> tools/testing/selftests/vfio/lib/sysfs.c | 3 +-
> tools/testing/selftests/vfio/lib/vfio_pci_device.c | 32 ++++++++++++----------
> .../vfio/vfio_pci_device_init_perf_test.c | 4 +--
> 6 files changed, 43 insertions(+), 30 deletions(-)
> ---
> base-commit: a26b499b757cfc8bbff1088bb1b844639e250893
> change-id: 20260612-scratch-amastro-vfio-selftests-avoid-vlas-395eb3dcb3ab
>
> Best regards,
> --
> Alex Mastro <amastro@fb.com>
>
Applied to vfio next branch for v7.3. Thanks,
Alex
prev parent reply other threads:[~2026-07-17 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 18:57 Alex Mastro
2026-06-17 18:58 ` [PATCH v4 1/2] vfio: selftests: Add allocation assert helpers Alex Mastro
2026-06-17 18:58 ` [PATCH v4 2/2] vfio: selftests: Avoid VLAs Alex Mastro
2026-06-17 22:55 ` [PATCH v4 0/2] vfio: selftests: Add allocation assert helpers and avoid VLAs David Matlack
2026-07-17 15:43 ` Alex Williamson [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=20260717094352.6bb38603@shazbot.org \
--to=alex@shazbot.org \
--cc=amastro@fb.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rananta@google.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vipinsh@google.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