All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Shawn Guo <shawnguo@kernel.org>
Subject: [GIT PULL] VLA removal leftovers for v4.19-rc1
Date: Thu, 16 Aug 2018 16:54:57 -0700	[thread overview]
Message-ID: <20180816235457.GA14528@beast> (raw)

Hi Linus,

Please pull these two VLA removals for v4.19-rc1. It didn't seem
sensible to me to wait to add these: they're both trivial and have been
sitting in -next while I tried to get them picked up by their respective
maintainers. Instead, I can just be that maintainer. :) After these,
only some core crypto VLA removals remain, as the series that fixes them
is still under review.

Thanks!

-Kees

The following changes since commit 7daf201d7fe8334e2d2364d4e8ed3394ec9af819:

  Linux 4.18-rc2 (2018-06-24 20:54:29 +0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/vla-leftovers-v4.19-rc1

for you to fetch changes up to d8dfa59f5a512a536b80a4a8f12fa993683f48df:

  bus: imx-weim: Remove VLA usage (2018-08-13 13:40:52 -0700)

----------------------------------------------------------------
VLA leftovers pull summary:

- bus/imx-weim: Use maximum register count to avoid VLA

- drm/i2c/tda9950: Use maximum CEC message size to avoid VLA

----------------------------------------------------------------
Kees Cook (2):
      drm/i2c: tda9950: Remove VLA usage
      bus: imx-weim: Remove VLA usage

 drivers/bus/imx-weim.c        | 7 ++++++-
 drivers/gpu/drm/i2c/tda9950.c | 5 ++++-
 2 files changed, 10 insertions(+), 2 deletions(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2018-08-16 23:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180816235457.GA14528@beast \
    --to=keescook@chromium.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=torvalds@linux-foundation.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.