public inbox for linux-kernel@vger.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,
	Christoph Hellwig <hch@infradead.org>,
	Trond Myklebust <trond.myklebust@primarydata.com>
Subject: [GIT PULL] gcc-plugin updates for v4.12-rc4
Date: Thu, 1 Jun 2017 13:25:33 -0700	[thread overview]
Message-ID: <20170601202533.GA124695@beast> (raw)

Hi,

Christoph Hellwig recommended that I send these fixes now, rather than
waiting for the v4.13 merge window. These are all initializer and cast
fixes needed for the future randstruct plugin that haven't been picked
up by the respective maintainers. If this is agreeable, please pull these
gcc-plugins updates for v4.12-rc4.

Thanks!

-Kees

The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:

  Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/gcc-plugins-v4.12-rc4

for you to fetch changes up to 243dd05d39aa14fac2ffde75cc66dee3270896f8:

  mtk-vcodec: Use designated initializers (2017-05-28 10:23:02 -0700)

----------------------------------------------------------------
Use designated initializers for mtk-vcodec, powerplay, amdgpu, and sgi-xp.
Use ERR_CAST() to avoid cross-structure cast in ocf2, ntfs, and NFS.

----------------------------------------------------------------
Kees Cook (7):
      NFS: Use ERR_CAST() to avoid cross-structure cast
      ntfs: Use ERR_CAST() to avoid cross-structure cast
      ocfs2: Use ERR_CAST() to avoid cross-structure cast
      sgi-xp: Use designated initializers
      drm/amdgpu: Use designated initializers
      drm/amd/powerplay: Use designated initializers
      mtk-vcodec: Use designated initializers

 drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c       | 10 +++---
 .../gpu/drm/amd/powerplay/hwmgr/vega10_thermal.c   | 20 ++++++------
 .../media/platform/mtk-vcodec/vdec/vdec_h264_if.c  |  8 ++---
 .../media/platform/mtk-vcodec/vdec/vdec_vp8_if.c   |  8 ++---
 .../media/platform/mtk-vcodec/vdec/vdec_vp9_if.c   |  8 ++---
 drivers/misc/sgi-xp/xp.h                           | 12 +++++++-
 drivers/misc/sgi-xp/xp_main.c                      | 36 +++++-----------------
 fs/nfs/namespace.c                                 |  2 +-
 fs/ntfs/namei.c                                    |  2 +-
 fs/ocfs2/export.c                                  |  2 +-
 10 files changed, 48 insertions(+), 60 deletions(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2017-06-01 20:25 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=20170601202533.GA124695@beast \
    --to=keescook@chromium.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trond.myklebust@primarydata.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