linux-kernel.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, Yue Hu <huyue2@yulong.com>
Subject: [GIT PULL] pstore updates for v5.1-rc1
Date: Mon, 4 Mar 2019 09:27:51 -0800	[thread overview]
Message-ID: <20190304172751.GA5887@beast> (raw)

Hi Linus,

Please pull these pstore changes for v5.1-rc1. These are some small
cleanups mostly in the ramoops backend.

Thanks!

-Kees

The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:

  Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v5.1-rc1

for you to fetch changes up to 93ee4b7d9f0632690713aee604c49e298e634094:

  pstore/ram: Avoid needless alloc during header write (2019-02-12 13:45:53 -0800)

----------------------------------------------------------------
pstore cleanups

- Remove some needless memory allocations (Yue Hu, Kees Cook)
- Add zero-length checks to avoid no-op calls (Yue Hu)

----------------------------------------------------------------
Kees Cook (1):
      pstore/ram: Avoid needless alloc during header write

Yue Hu (4):
      pstore/ram: Replace dummy_data heap memory with stack memory
      pstore: Avoid writing records with zero size
      pstore/ram: Move initialization earlier
      pstore/ram: Add kmsg hlen zero check to ramoops_pstore_write()

 fs/pstore/platform.c |  3 +++
 fs/pstore/ram.c      | 64 ++++++++++++++++++++++++----------------------------
 2 files changed, 32 insertions(+), 35 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2019-03-04 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 17:27 Kees Cook [this message]
2019-03-09 19:55 ` [GIT PULL] pstore updates for v5.1-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=20190304172751.GA5887@beast \
    --to=keescook@chromium.org \
    --cc=huyue2@yulong.com \
    --cc=linux-kernel@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).