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,
	Dan Carpenter <dan.carpenter@oracle.com>,
	"Joel Fernandes (Google)" <joel@joelfernandes.org>,
	Peng Wang <wangpeng15@xiaomi.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Meyer <thomas@m3y3r.de>
Subject: [GIT PULL] pstore updates for v4.21-rc1
Date: Mon, 17 Dec 2018 15:50:40 -0800	[thread overview]
Message-ID: <20181217235040.GA18678@beast> (raw)

Hi Linus,

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

Thanks!

-Kees

The following changes since commit ccda4af0f4b92f7b4c308d3acc262f4a7e3affad:

  Linux 4.20-rc2 (2018-11-11 17:12:31 -0600)

are available in the Git repository at:

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

for you to fetch changes up to 8665569e97dd52920713b95675409648986b5b0d:

  pstore/ram: Avoid NULL deref in ftrace merging failure path (2018-12-03 17:11:02 -0800)

----------------------------------------------------------------
pstore improvements and refactorings

- Improve compression handling
- Refactor argument handling during initialization
- Avoid needless locking for saner EFI backend handling
- Add more kern-doc and improve debugging output

----------------------------------------------------------------
Joel Fernandes (Google) (3):
      pstore: Map PSTORE_TYPE_* to strings
      pstore/ram: Simplify ramoops_get_next_prz() arguments
      pstore/ram: Do not treat empty buffers as valid

Kees Cook (11):
      pstore/ram: Correctly calculate usable PRZ bytes
      Merge branch 'for-linus/pstore' into for-next/pstore
      pstore: Do not use crash buffer for decompression
      pstore: Remove needless lock during console writes
      pstore/ram: Standardize module name in ramoops
      pstore/ram: Report backend assignments with finer granularity
      pstore/ram: Add kern-doc for struct persistent_ram_zone
      pstore: Improve and update some comments and status output
      pstore: Replace open-coded << with BIT()
      pstore: Convert buf_lock to semaphore
      pstore/ram: Avoid NULL deref in ftrace merging failure path

Peng Wang (1):
      pstore: Avoid duplicate call of persistent_ram_zap()

Thomas Meyer (1):
      pstore: Fix bool initialization/comparison

 arch/powerpc/kernel/nvram_64.c    |   2 -
 drivers/acpi/apei/erst.c          |   3 +-
 drivers/firmware/efi/efi-pstore.c |   4 +-
 fs/pstore/ftrace.c                |   2 +-
 fs/pstore/inode.c                 |  51 +----------
 fs/pstore/platform.c              | 173 +++++++++++++++++++++-----------------
 fs/pstore/ram.c                   |  78 +++++++----------
 fs/pstore/ram_core.c              |  45 ++++++++--
 include/linux/pstore.h            |  39 ++++++---
 include/linux/pstore_ram.h        |  50 ++++++++++-
 10 files changed, 241 insertions(+), 206 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2018-12-17 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 23:50 Kees Cook [this message]
2018-12-27 22:05 ` [GIT PULL] pstore updates for v4.21-rc1 pr-tracker-bot

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=20181217235040.GA18678@beast \
    --to=keescook@chromium.org \
    --cc=bigeasy@linutronix.de \
    --cc=dan.carpenter@oracle.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    --cc=torvalds@linux-foundation.org \
    --cc=wangpeng15@xiaomi.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 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.