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,
	Ankit Kumar <ankit@linux.vnet.ibm.com>,
	Anton Blanchard <anton@au1.ibm.com>,
	Douglas Anderson <dianders@chromium.org>,
	Geliang Tang <geliangtang@gmail.com>,
	Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Subject: [GIT PULL] pstore updates for v4.13-rc1
Date: Tue, 4 Jul 2017 21:29:46 -0700	[thread overview]
Message-ID: <20170705042946.GA71633@beast> (raw)

Hi,

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

Thanks!

-Kees

The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b:

  Linux 4.12-rc3 (2017-05-28 17:20:53 -0700)

are available in the git repository at:

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

for you to fetch changes up to 0752e4028c003fba1e2b44c4b3cf6a4482e931b6:

  powerpc/nvram: use memdup_user (2017-06-27 17:02:50 -0700)

----------------------------------------------------------------
Various fixes and tweaks for the pstore subsystem. Highlights:
- use memdup_user() instead of open-coded copies (Geliang Tang)
- fix record memory leak during initialization (Douglas Anderson)
- avoid confused compressed record warning (Ankit Kumar)
- prepopulate record timestamp and remove redundant logic from backends

----------------------------------------------------------------
Ankit Kumar (1):
      pstore: Don't warn if data is uncompressed and type is not PSTORE_TYPE_DMESG

Douglas Anderson (1):
      pstore: Fix leaked pstore_record in pstore_get_backend_records()

Geliang Tang (2):
      pstore: use memdup_user
      powerpc/nvram: use memdup_user

Kees Cook (5):
      pstore: Avoid potential infinite loop
      efi-pstore: Refactor erase routine
      pstore: Create common record initializer
      pstore: Populate pstore record->time field
      pstore: Fix format string to use %u for record id

 arch/powerpc/kernel/nvram_64.c    | 14 +++----
 drivers/firmware/efi/efi-pstore.c | 87 +++++++++++++++++----------------------
 fs/pstore/inode.c                 | 22 +++++-----
 fs/pstore/internal.h              |  2 +
 fs/pstore/platform.c              | 69 ++++++++++++++++++++-----------
 fs/pstore/pmsg.c                  | 10 ++---
 fs/pstore/ram.c                   | 16 +++----
 include/linux/pstore.h            |  5 ++-
 8 files changed, 114 insertions(+), 111 deletions(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2017-07-05  4:29 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=20170705042946.GA71633@beast \
    --to=keescook@chromium.org \
    --cc=ankit@linux.vnet.ibm.com \
    --cc=anton@au1.ibm.com \
    --cc=dianders@chromium.org \
    --cc=geliangtang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh@linux.vnet.ibm.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.