From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Nick Kralevich <nnk@google.com>, Petr Mladek <pmladek@suse.cz>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [GIT PULL] pstore updates for v4.14-rc1
Date: Tue, 5 Sep 2017 12:51:30 -0700 [thread overview]
Message-ID: <20170905195130.GA72053@beast> (raw)
Hi,
Please pull these pstore changes for v4.14-rc1. Not much happening in
pstore for this release. One change to permission management, noted below.
Thanks!
-Kees
The following changes since commit 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9:
Linux 4.13-rc2 (2017-07-23 16:15:17 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v4.14-rc1
for you to fetch changes up to c71b02e4d207cbcf097f9746d5f7967b22905e70:
Revert "pstore: Honor dmesg_restrict sysctl on dmesg dumps" (2017-08-17 16:29:19 -0700)
----------------------------------------------------------------
Make pstore permissions more versatile by removing CAP_SYSLOG requirement
and defining more restrictive root directory DAC permissions default
(0750, which can be adjust after boot unlike the CAP_SYSLOG check).
Suggested by Nick Kralevich.
----------------------------------------------------------------
Kees Cook (2):
pstore: Make default pstorefs root dir perms 0750
Revert "pstore: Honor dmesg_restrict sysctl on dmesg dumps"
fs/pstore/inode.c | 24 +-----------------------
include/linux/syslog.h | 9 ---------
kernel/printk/printk.c | 3 +--
3 files changed, 2 insertions(+), 34 deletions(-)
--
Kees Cook
Pixel Security
reply other threads:[~2017-09-05 19:51 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=20170905195130.GA72053@beast \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nnk@google.com \
--cc=pmladek@suse.cz \
--cc=sergey.senozhatsky@gmail.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