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>,
	Geliang Tang <geliangtang@gmail.com>,
	Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] pstore updates for v4.17-rc1
Date: Mon, 2 Apr 2018 09:26:26 -0700	[thread overview]
Message-ID: <20180402162626.GA27422@beast> (raw)

Hi Linus,

Please pull these pstore changes for v4.17-rc1. This cycle was almost
entirely improvements to the pstore compression options, noted below.

Thanks!

-Kees

The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:

  Linux 4.16-rc2 (2018-02-18 17:29:42 -0800)

are available in the git repository at:

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

for you to fetch changes up to 58eb5b6707477ff458db3ee522aac317da719e2a:

  pstore: fix crypto dependencies (2018-03-15 10:06:06 -0700)

----------------------------------------------------------------
- Add lz4hc and 842 to pstore compression options (Geliang Tang)
- Refactor to use crypto compression API (Geliang Tang)
- Fix up Kconfig dependencies for compression (Arnd Bergmann)
- Allow for run-time compression selection
- Remove stack VLA usage

----------------------------------------------------------------
Arnd Bergmann (1):
      pstore: fix crypto dependencies

Geliang Tang (2):
      pstore: Add lz4hc and 842 compression support
      pstore: Use crypto compress API

Kees Cook (3):
      pstore: Avoid size casts for 842 compression
      pstore: Select compression at runtime
      pstore/ram: Do not use stack VLA for parity workspace

 fs/pstore/Kconfig          | 101 +++++++++---
 fs/pstore/inode.c          |   2 +
 fs/pstore/internal.h       |   3 +
 fs/pstore/platform.c       | 372 +++++++++++++++------------------------------
 fs/pstore/ram.c            |   2 +-
 fs/pstore/ram_core.c       |  29 +++-
 include/linux/pstore_ram.h |   1 +
 7 files changed, 226 insertions(+), 284 deletions(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2018-04-02 16:26 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=20180402162626.GA27422@beast \
    --to=keescook@chromium.org \
    --cc=arnd@arndb.de \
    --cc=geliangtang@gmail.com \
    --cc=linux-kernel@vger.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.