From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] pstore fix for v6.6-rc1
Date: Fri, 1 Sep 2023 11:27:10 -0700 [thread overview]
Message-ID: <202309011125.B1C2550792@keescook> (raw)
Hi Linus,
Please pull this pstore fix for v6.6-rc1. This should solve the
issues[1] you saw after the initial v6.6-rc1 pull.
Thanks!
-Kees
[1] https://lore.kernel.org/lkml/CAHk-=wi_WxZ2dEsQR0-wDtYAh4sxVEQkU7HK5JSboVv7v7NwcQ@mail.gmail.com/
The following changes since commit af58740d8b06a6a97b7594235a1be11bd6aa37fa:
pstore: Fix kernel-doc warning (2023-08-18 13:27:28 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v6.6-rc1-fix
for you to fetch changes up to 94160062396d7e7cff4ed69320ffc5e22d51a0ab:
pstore: Base compression input buffer size on estimated compressed size (2023-08-31 13:58:49 -0700)
----------------------------------------------------------------
pstore fix for v6.6-rc1
- Adjust sizes of buffers just avoid uncompress failures (Ard Biesheuvel)
----------------------------------------------------------------
Ard Biesheuvel (1):
pstore: Base compression input buffer size on estimated compressed size
fs/pstore/platform.c | 34 +++++++++++++++++++++++++++-------
1 file changed, 27 insertions(+), 7 deletions(-)
--
Kees Cook
next reply other threads:[~2023-09-01 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:27 Kees Cook [this message]
2023-09-02 18:48 ` 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=202309011125.B1C2550792@keescook \
--to=keescook@chromium.org \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--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 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®