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, Aaron Durbin <adurbin@chromium.org>,
	Andrew Bresticker <abrestic@chromium.org>,
	Enric Balletbo Serra <enric.balletbo@collabora.com>,
	Furquan Shaikh <furquan@chromium.org>,
	Furquan Shaikh <furquan@google.com>,
	Geliang Tang <geliangtang@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Kees Cook <keescook@chromium.org>,
	Mark Salyzyn <salyzyn@android.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Olof Johansson <olofj@chromium.org>,
	Puneet Kumar <puneetster@chromium.org>,
	Rabin Vincent <rabinv@axis.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [GIT PULL] pstore updates for v4.9-rc1
Date: Wed, 5 Oct 2016 14:43:58 -0700	[thread overview]
Message-ID: <20161005214358.GA52681@beast> (raw)

Hi,

Please pull these pstore changes for v4.9-rc1.

Thanks!

-Kees

The following changes since commit d71f058617564750261b673ea9b3352382b9cde4:

  Merge branch 'for-rc' of git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux (2016-09-07 21:28:26 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v4.9-rc1

for you to fetch changes up to f88baf68ebe5b2efced64725fd98548af9b8f510:

  ramoops: move spin_lock_init after kmalloc error checking (2016-09-08 15:01:13 -0700)

----------------------------------------------------------------
Fix bug in module unloading.
Switch to always using spinlock over cmpxchg.
Explicitly define pstore backend's supported modes.
Remove bounce buffer from pmsg.
Switch to using memcpy_to/fromio().
Error checking improvements.

----------------------------------------------------------------
Andrew Bresticker (1):
      pstore/ram: Use memcpy_fromio() to save old buffer

Furquan Shaikh (1):
      pstore/ram: Use memcpy_toio instead of memcpy

Geliang Tang (1):
      ramoops: move spin_lock_init after kmalloc error checking

Mark Salyzyn (1):
      pstore/pmsg: drop bounce buffer

Namhyung Kim (2):
      pstore: Split pstore fragile flags
      pstore/ram: Set pstore flags dynamically

Sebastian Andrzej Siewior (2):
      pstore/ramoops: fixup driver removal
      pstore/core: drop cmpxchg based updates

 drivers/acpi/apei/erst.c          |  2 +-
 drivers/firmware/efi/efi-pstore.c |  2 +-
 fs/pstore/platform.c              | 53 ++++++++++++++++++---
 fs/pstore/pmsg.c                  | 35 +++-----------
 fs/pstore/ram.c                   | 46 ++++++++++++++++---
 fs/pstore/ram_core.c              | 96 ++++++++++++++++++++-------------------
 include/linux/pstore.h            | 17 +++++--
 include/linux/pstore_ram.h        |  7 ++-
 8 files changed, 162 insertions(+), 96 deletions(-)

-- 
Kees Cook
Nexus Security

                 reply	other threads:[~2016-10-05 21:44 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=20161005214358.GA52681@beast \
    --to=keescook@chromium.org \
    --cc=abrestic@chromium.org \
    --cc=adurbin@chromium.org \
    --cc=bigeasy@linutronix.de \
    --cc=enric.balletbo@collabora.com \
    --cc=furquan@chromium.org \
    --cc=furquan@google.com \
    --cc=geliangtang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=namhyung@kernel.org \
    --cc=olofj@chromium.org \
    --cc=puneetster@chromium.org \
    --cc=rabinv@axis.com \
    --cc=salyzyn@android.com \
    --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.