From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Joel Fernandes <joelaf@google.com>,
Li Pengcheng <lipengcheng8@huawei.com>,
Liu Hailong <liuhailong5@huawei.com>,
Li Zhong <lizhong11@hisilicon.com>,
Namhyung Kim <namhyung@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [GIT PULL] pstore updates for v4.10-rc1
Date: Wed, 7 Dec 2016 15:35:53 -0800 [thread overview]
Message-ID: <20161207233553.GA66972@beast> (raw)
Hi,
As requested, here's an early pull request for v4.10. :) Please pull these
pstore changes for v4.10-rc1.
Thanks!
-Kees
The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69:
Linux 4.9-rc2 (2016-10-23 17:10:14 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v4.10-rc1
for you to fetch changes up to fc46d4e453f50d2b376267f180cae250b54f9fb4:
ramoops: add pdata NULL check to ramoops_probe (2016-11-15 16:34:32 -0800)
----------------------------------------------------------------
Improvements and fixes to pstore subsystem:
- Add additional checks for bad platform data
- Remove bounce buffer in console writer
- Protect read/unlink race with a mutex
- Correctly give up during dump locking failures
- Increase ftrace bandwidth by splitting ftrace buffers per CPU
----------------------------------------------------------------
Joel Fernandes (8):
pstore: Make spinlock per zone instead of global
pstore: Warn on PSTORE_TYPE_PMSG using deprecated function
pstore: Allow prz to control need for locking
ramoops: Split ftrace buffer space into per-CPU zones
pstore: Add ftrace timestamp counter
pstore: Merge per-CPU ftrace records into one
ftrace: Provide API to use global filtering for ftrace ops
pstore: Use global ftrace filters for function trace filtering
Kees Cook (4):
pstore: Make ramoops_init_przs generic for other prz arrays
pstore: improve error report for failed setup
pstore: Clarify context field przs as dprzs
ramoops: add pdata NULL check to ramoops_probe
Li Pengcheng (1):
pstore: Actually give up during locking failure
Namhyung Kim (2):
pstore: Protect unlink with read_mutex
pstore: Convert console write to use ->write_buf
.../bindings/reserved-memory/ramoops.txt | 3 +
fs/pstore/ftrace.c | 11 +-
fs/pstore/inode.c | 15 +-
fs/pstore/internal.h | 34 ---
fs/pstore/platform.c | 5 +-
fs/pstore/ram.c | 327 ++++++++++++++++-----
fs/pstore/ram_core.c | 27 +-
include/linux/ftrace.h | 2 +
include/linux/pstore.h | 76 +++++
include/linux/pstore_ram.h | 14 +-
kernel/trace/ftrace.c | 17 ++
11 files changed, 404 insertions(+), 127 deletions(-)
--
Kees Cook
Nexus Security
reply other threads:[~2016-12-07 23:35 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=20161207233553.GA66972@beast \
--to=keescook@chromium.org \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lipengcheng8@huawei.com \
--cc=liuhailong5@huawei.com \
--cc=lizhong11@hisilicon.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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.