From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Douglas Anderson <dianders@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Norbert Manthey <nmanthey@amazon.de>,
Tony Luck <tony.luck@intel.com>
Subject: [GIT PULL] pstore updates for v5.3-rc1
Date: Mon, 8 Jul 2019 21:11:18 -0700 [thread overview]
Message-ID: <201907082110.3C6AF83FA@keescook> (raw)
Hi Linus,
Please pull these pstore updates for v5.3-rc1. Details below...
Thanks!
-Kees
The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v5.3-rc1
for you to fetch changes up to 4c6d80e1144bdf48cae6b602ae30d41f3e5c76a9:
pstore: Fix double-free in pstore_mkfile() failure path (2019-07-08 21:04:42 -0700)
----------------------------------------------------------------
pstore improvements
- Improve backward compatibility with older Chromebooks (Douglas Anderson)
- Refactor debugfs initialization (Greg KH)
- Fix double-free in pstore_mkfile() failure path (Norbert Manthey)
----------------------------------------------------------------
Douglas Anderson (1):
pstore/ram: Improve backward compatibility with older Chromebooks
Greg Kroah-Hartman (1):
pstore: no need to check return value of debugfs_create functions
Norbert Manthey (1):
pstore: Fix double-free in pstore_mkfile() failure path
fs/pstore/ftrace.c | 18 ++----------------
fs/pstore/inode.c | 13 ++++++-------
fs/pstore/ram.c | 21 +++++++++++++++++++++
3 files changed, 29 insertions(+), 23 deletions(-)
--
Kees Cook
next reply other threads:[~2019-07-09 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 4:11 Kees Cook [this message]
2019-07-11 22:30 ` [GIT PULL] pstore updates for v5.3-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=201907082110.3C6AF83FA@keescook \
--to=keescook@chromium.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmanthey@amazon.de \
--cc=tony.luck@intel.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 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).