From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Aleksandr Yashkin <a.yashkin@inango-systems.com>,
Ariel Gilman <a.gilman@inango-systems.com>,
Navid Emamdoost <navid.emamdoost@gmail.com>,
Nikolay Merinov <n.merinov@inango-systems.com>
Subject: [GIT PULL] pstore fixes for v5.5-rc5
Date: Thu, 2 Jan 2020 12:55:08 -0800 [thread overview]
Message-ID: <202001021254.2F43E8A@keescook> (raw)
Hi Linus,
Please pull these two pstore fixes for v5.5-rc5.
Thanks!
-Kees
The following changes since commit d1eef1c619749b2a57e514a3fa67d9a516ffa919:
Linux 5.5-rc2 (2019-12-15 15:16:08 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v5.5-rc5
for you to fetch changes up to 9e5f1c19800b808a37fb9815a26d382132c26c3d:
pstore/ram: Write new dumps to start of recycled zones (2020-01-02 12:30:50 -0800)
----------------------------------------------------------------
pstore bug fixes
- always reset circular buffer state when writing new dump (Aleksandr Yashkin)
- fix rare error-path memory leak (Kees Cook)
----------------------------------------------------------------
Aleksandr Yashkin (1):
pstore/ram: Write new dumps to start of recycled zones
Kees Cook (1):
pstore/ram: Fix error-path memory leak in persistent_ram_new() callers
fs/pstore/ram.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
--
Kees Cook
next reply other threads:[~2020-01-02 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 20:55 Kees Cook [this message]
2020-01-03 1:25 ` [GIT PULL] pstore fixes for v5.5-rc5 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=202001021254.2F43E8A@keescook \
--to=keescook@chromium.org \
--cc=a.gilman@inango-systems.com \
--cc=a.yashkin@inango-systems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n.merinov@inango-systems.com \
--cc=navid.emamdoost@gmail.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;
as well as URLs for NNTP newsgroup(s).