public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Liu ShuoX <shuox.liu@intel.com>
Subject: [GIT PULL] pstore fixes for 3.15
Date: Tue, 01 Apr 2014 16:36:22 -0700	[thread overview]
Message-ID: <533b4d76301489fdd4@agluck-desk.sc.intel.com> (raw)

The following changes since commit dcb99fd9b08cfe1afe426af4d8d3cbc429190f15:

  Linux 3.14-rc7 (2014-03-16 18:51:24 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git tags/please-pull-pstore

for you to fetch changes up to e32634f5d57f1dce88624b70a6d625915f6ea09e:

  pstore: Fix memory leak when decompress using big_oops_buf (2014-03-17 14:14:03 -0700)

----------------------------------------------------------------
Series of small bug fixes for pstore.

----------------------------------------------------------------
Liu ShuoX (6):
      pstore: clarify clearing of _read_cnt in ramoops_context
      pstore: skip zero size persistent ram buffer in traverse
      pstore: Fix NULL pointer fault if get NULL prz in ramoops_get_next_prz
      pstore: Correct the max_dump_cnt clearing of ramoops
      pstore: Fix buffer overflow while write offset equal to buffer size
      pstore: Fix memory leak when decompress using big_oops_buf

 fs/pstore/platform.c |  1 +
 fs/pstore/ram.c      | 19 +++++++++++--------
 fs/pstore/ram_core.c |  4 ++--
 3 files changed, 14 insertions(+), 10 deletions(-)

                 reply	other threads:[~2014-04-01 23:36 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=533b4d76301489fdd4@agluck-desk.sc.intel.com \
    --to=tony.luck@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuox.liu@intel.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