All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Cengiz Can <cengiz@kernel.wtf>
Subject: [GIT PULL] pstore fix for v5.5-rc6
Date: Thu, 9 Jan 2020 20:46:57 -0800	[thread overview]
Message-ID: <202001092044.EE43B805@keescook> (raw)

Hi Linus,

Please pull this pstore fix for v5.5-rc6. Cengiz Can forwarded a Coverity
report about more problems with a rare pstore initialization error path,
so the allocation lifetime was rearranged to avoid needing to share the
kfree() responsibilities between caller and callee.

Thanks!

-Kees

The following changes since commit 9e5f1c19800b808a37fb9815a26d382132c26c3d:

  pstore/ram: Write new dumps to start of recycled zones (2020-01-02 12:30:50 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v5.5-rc6

for you to fetch changes up to e163fdb3f7f8c62dccf194f3f37a7bcb3c333aa8:

  pstore/ram: Regularize prz label allocation lifetime (2020-01-08 17:05:45 -0800)

----------------------------------------------------------------
pstore fix for rare error path

- Fix label allocation lifetime/visibility to avoid further mistakes

----------------------------------------------------------------
Kees Cook (1):
      pstore/ram: Regularize prz label allocation lifetime

 fs/pstore/ram.c      | 4 ++--
 fs/pstore/ram_core.c | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2020-01-10  4:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10  4:46 Kees Cook [this message]
2020-01-11 14:45 ` [GIT PULL] pstore fix for v5.5-rc6 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=202001092044.EE43B805@keescook \
    --to=keescook@chromium.org \
    --cc=cengiz@kernel.wtf \
    --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 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.