From: Vinod Koul <vinod.koul@intel.com>
To: Laura Abbott <labbott@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Kees Cook <keescook@chromium.org>,
Sinan Kaya <okaya@codeaurora.org>
Subject: [PATCHv2] dmaengine: dmatest: Remove use of VLAs
Date: Mon, 16 Apr 2018 21:06:34 +0530 [thread overview]
Message-ID: <20180416153634.GR6014@localhost> (raw)
On Tue, Apr 10, 2018 at 06:02:16PM -0700, Laura Abbott wrote:
> There's an ongoing effort to remove VLAs from the kernel
> (https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla.
> The test already pre-allocates some buffers with kmalloc so turn
> the two VLAs in to pre-allocated kmalloc buffers.
Applied, thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Laura Abbott <labbott@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Kees Cook <keescook@chromium.org>,
Sinan Kaya <okaya@codeaurora.org>
Subject: Re: [PATCHv2] dmaengine: dmatest: Remove use of VLAs
Date: Mon, 16 Apr 2018 21:06:34 +0530 [thread overview]
Message-ID: <20180416153634.GR6014@localhost> (raw)
In-Reply-To: <20180411010216.17702-1-labbott@redhat.com>
On Tue, Apr 10, 2018 at 06:02:16PM -0700, Laura Abbott wrote:
> There's an ongoing effort to remove VLAs from the kernel
> (https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla.
> The test already pre-allocates some buffers with kmalloc so turn
> the two VLAs in to pre-allocated kmalloc buffers.
Applied, thanks
--
~Vinod
next reply other threads:[~2018-04-16 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 15:36 Vinod Koul [this message]
2018-04-16 15:36 ` [PATCHv2] dmaengine: dmatest: Remove use of VLAs Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-04-12 2:26 Sinan Kaya
2018-04-12 2:26 ` Sinan Kaya
2018-04-11 1:02 Laura Abbott
2018-04-11 1:02 ` Laura Abbott
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=20180416153634.GR6014@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.