mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Andrea Parri <parri.andrea@gmail.com>,
	Jaidev Shastri <jaidevshastri@vt.edu>,
	Kees Cook <kees@kernel.org>
Subject: [GIT PULL] pstore updates for v7.4-rc1
Date: Thu, 22 Oct 2026 10:49:37 -0700	[thread overview]
Message-ID: <202610221048.DB2F64A17@keescook> (raw)

Hi Linus,

Please pull these pstore updates for v7.4-rc1. They're mainly fixes for
error handling and corner cases.

Thanks!

-Kees

The following changes since commit df2908090cda368b01ff43709f51890076c56157:

  Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v7.4-rc1

for you to fetch changes up to 7c756181175d50200be487affa905e973f6cbaf5:

  pstore: publish big_oops_buf after max_compressed_size (2026-09-21 20:55:04 -0700)

----------------------------------------------------------------
pstore updates for v7.4-rc1

- don't leave an ERR_PTR in the ramoops zone pointer (Andrea Parri)

- reject persistent RAM zones too small for the buffer header (Andrea Parri)

- publish big_oops_buf after max_compressed_size (Jaidev Shastri)

----------------------------------------------------------------
Andrea Parri (2):
      pstore: don't leave an ERR_PTR in the ramoops zone pointer
      pstore: reject persistent RAM zones too small for the buffer header

Jaidev Shastri (1):
      pstore: publish big_oops_buf after max_compressed_size

 fs/pstore/platform.c | 12 +++++++++---
 fs/pstore/ram.c      |  1 +
 fs/pstore/ram_core.c |  6 ++++++
 3 files changed, 16 insertions(+), 3 deletions(-)

-- 
Kees Cook

                 reply	other threads:[~2026-10-22 17:49 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=202610221048.DB2F64A17@keescook \
    --to=kees@kernel.org \
    --cc=jaidevshastri@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parri.andrea@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

all inboxes | Powered by JetHome®