All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Anton Vorontsov <anton@enomsg.org>,
	Colin Cross <ccross@android.com>,
	Geliang Tang <geliangtang@gmail.com>,
	Joel Fernandes <joelaf@google.com>,
	nixiaoming <nixiaoming@huawei.com>,
	Tony Luck <tony.luck@intel.com>
Subject: [GIT PULL] pstore fix for v4.19-rc7
Date: Sun, 30 Sep 2018 10:29:07 -0700	[thread overview]
Message-ID: <20180930172907.GA3543@beast> (raw)

Hi Greg,

Please pull this pstore fix for v4.19-rc7.

Thanks!

-Kees

The following changes since commit 831b624df1b420c8f9281ed1307a8db23afb72df:

  pstore: Fix incorrect persistent ram buffer mapping (2018-09-13 09:14:57 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v4.19-rc7

for you to fetch changes up to bac6f6cda206ad7cbe0c73c35e494377ce9c4749:

  pstore/ram: Fix failure-path memory leak in ramoops_init (2018-09-30 10:15:41 -0700)

----------------------------------------------------------------
Fixes for v4.19-rc7

- Fix failure-path memory leak in ramoops_init (nixiaoming)

----------------------------------------------------------------
Kees Cook (1):
      pstore/ram: Fix failure-path memory leak in ramoops_init

 fs/pstore/ram.c | 29 +++++++++++++++++++++++++----
 1 file changed, 25 insertions(+), 4 deletions(-)

-- 
Kees Cook
Pixel Security

             reply	other threads:[~2018-09-30 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30 17:29 Kees Cook [this message]
2018-10-02  0:53 ` [GIT PULL] pstore fix for v4.19-rc7 Greg KH

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=20180930172907.GA3543@beast \
    --to=keescook@chromium.org \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=geliangtang@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joelaf@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nixiaoming@huawei.com \
    --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 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.