linux-kernel - [GIT PULL] pstore fixes for 3.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <533b4d76301489fdd4@agluck-desk.sc.intel.com>
Date:	Tue, 01 Apr 2014 16:36:22 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Liu ShuoX <shuox.liu@...el.com>
Subject: [GIT PULL] pstore fixes for 3.15

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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/