From: Kees Cook <keescook@chromium.org>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH RFC v2 0/3] cleanups for pstore and ramoops
Date: Wed, 14 Nov 2018 01:14:57 -0600 [thread overview]
Message-ID: <CAGXu5jJ3s=pXGaEVLycdV6TYScUmPqhChNBS92j2qUxct2+ZrQ@mail.gmail.com> (raw)
In-Reply-To: <20181103233818.44615-1-joel@joelfernandes.org>
On Sat, Nov 3, 2018 at 6:38 PM, Joel Fernandes (Google)
<joel@joelfernandes.org> wrote:
> Here are some simple cleanups and fixes for ramoops in pstore. Let me know
> what you think, thanks.
I took these and slightly tweaked code locations for the first one.
I'll send out the series for review when I'm back from Plumber's.
-Kees
>
> Joel Fernandes (Google) (3):
> pstore: map pstore types to names
> pstore: simplify ramoops_get_next_prz arguments
> pstore: donot treat empty buffers as valid
>
> fs/pstore/inode.c | 53 +++++---------------------------------
> fs/pstore/ram.c | 52 +++++++++++++++----------------------
> fs/pstore/ram_core.c | 2 +-
> include/linux/pstore.h | 37 ++++++++++++++++++++++++++
> include/linux/pstore_ram.h | 2 ++
> 5 files changed, 67 insertions(+), 79 deletions(-)
>
> --
> 2.19.1.930.g4563a0d9d0-goog
>
--
Kees Cook
next prev parent reply other threads:[~2018-11-14 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 23:38 [PATCH RFC v2 0/3] cleanups for pstore and ramoops Joel Fernandes (Google)
2018-11-03 23:38 ` [PATCH RFC v2 1/3] pstore: map pstore types to names Joel Fernandes (Google)
2018-11-05 4:46 ` Joel Fernandes
2018-11-03 23:38 ` [PATCH RFC v2 2/3] pstore: simplify ramoops_get_next_prz arguments Joel Fernandes (Google)
2018-11-03 23:38 ` [PATCH RFC v2 3/3] pstore: donot treat empty buffers as valid Joel Fernandes (Google)
2018-11-14 7:14 ` Kees Cook [this message]
2018-11-15 2:20 ` [PATCH RFC v2 0/3] cleanups for pstore and ramoops Joel Fernandes
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='CAGXu5jJ3s=pXGaEVLycdV6TYScUmPqhChNBS92j2qUxct2+ZrQ@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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).