From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: linux-hyperv@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
kernel-janitors@vger.kernel.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
John Stultz <jstultz@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-sgx@vger.kernel.org, Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
kasan-dev@googlegroups.com, iommu@lists.linux.dev,
kuba@kernel.org, Laura Abbott <labbott@redhat.com>,
linux-media@vger.kernel.org, keescook@chromium.org,
linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, Krishna Reddy <vdumpa@nvidia.com>,
Shailend Chand <shailend@google.com>,
christophe.jaillet@wanadoo.fr, linux-tegra@vger.kernel.org,
intel-gvt-dev@lists.freedesktop.org,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Mark <lmark@codeaurora.org>,
mhi@lists.linux.dev, Robin Murphy <robin.murphy@arm.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2 00/24] use vmalloc_array and vcalloc
Date: Wed, 05 Jul 2023 21:35:55 -0400 [thread overview]
Message-ID: <yq1pm55lt3y.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230627144339.144478-1-Julia.Lawall@inria.fr> (Julia Lawall's message of "Tue, 27 Jun 2023 16:43:15 +0200")
Julia,
> The functions vmalloc_array and vcalloc were introduced in
>
> commit a8749a35c399 ("mm: vmalloc: introduce array allocation functions")
>
> but are not used much yet. This series introduces uses of
> these functions, to protect against multiplication overflows.
Applied #7 and #24 to 6.5/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-07-06 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 14:43 [Intel-gfx] [PATCH v2 00/24] use vmalloc_array and vcalloc Julia Lawall
2023-06-27 14:43 ` [Intel-gfx] [PATCH v2 16/24] drm/i915/gvt: " Julia Lawall
2023-06-27 16:40 ` [Intel-gfx] [PATCH v2 00/24] " patchwork-bot+netdevbpf
2023-07-06 1:35 ` Martin K. Petersen [this message]
2023-07-11 16:31 ` [Intel-gfx] (subset) " Martin K. Petersen
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=yq1pm55lt3y.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=Julia.Lawall@inria.fr \
--cc=andreyknvl@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dave.hansen@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jstultz@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=mhi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=shailend@google.com \
--cc=vdumpa@nvidia.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.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