stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Pi-Hsun Shih <pihsun@chromium.org>,
	stable@vger.kernel.org
Subject: [GIT PULL] pstore fixes for v5.2-rc4
Date: Tue, 4 Jun 2019 20:20:21 -0700	[thread overview]
Message-ID: <201906042018.72255CAF94@keescook> (raw)

Hi Linus,

Please pull these pstore fixes for v5.2-rc4. They've been in linux-next
for a bit now and catch some pstore corner cases found recently.

Thanks!

-Kees

The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:

  Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v5.2-rc4

for you to fetch changes up to 8880fa32c557600f5f624084152668ed3c2ea51e:

  pstore/ram: Run without kernel crash dump region (2019-05-31 01:19:06 -0700)

----------------------------------------------------------------
pstore fixes for v5.2-rc4

- Avoid NULL deref when unloading/reloading ramoops module (Pi-Hsun Shih)
- Run ramoops without crash dump region

----------------------------------------------------------------
Kees Cook (1):
      pstore/ram: Run without kernel crash dump region

Pi-Hsun Shih (1):
      pstore: Set tfm to NULL on free_buf_for_compression

 fs/pstore/platform.c |  7 +++++--
 fs/pstore/ram.c      | 36 +++++++++++++++++++++++-------------
 2 files changed, 28 insertions(+), 15 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2019-06-05  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  3:20 Kees Cook [this message]
2019-06-05 21:05 ` [GIT PULL] pstore fixes for v5.2-rc4 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=201906042018.72255CAF94@keescook \
    --to=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pihsun@chromium.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).