From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
Tony Luck <tony.luck@intel.com>,
Weichen Chen <weichen.chen@mediatek.com>
Subject: [GIT PULL] pstore updates for v6.8-rc1
Date: Mon, 8 Jan 2024 10:24:29 -0800 [thread overview]
Message-ID: <202401081022.31D251086@keescook> (raw)
Hi Linus,
Please pull these pstore updates for v6.8-rc1. These are a couple small
fixes, and a refactoring to use cleanup.h now that it has had time to
bake in a full release.
Thanks!
-Kees
The following changes since commit 98b1cc82c4affc16f5598d4fa14b1858671b2263:
Linux 6.7-rc2 (2023-11-19 15:02:14 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v6.8-rc1
for you to fetch changes up to 24a0b5e196cf70ccff97bc0add6fa7178ad50cc4:
pstore: inode: Use cleanup.h for struct pstore_private (2023-12-08 14:15:44 -0800)
----------------------------------------------------------------
pstore updates for v6.8-rc1
- Do not allow misconfigured ECC sizes (Sergey Shtylyov)
- Allow for odd number of CPUs (Weichen Chen)
- Refactor error handling to use cleanup.h
----------------------------------------------------------------
Kees Cook (4):
pstore: inode: Convert kfree() usage to __free(kfree)
pstore: inode: Convert mutex usage to guard(mutex)
pstore: inode: Use __free(pstore_iput) for inode allocations
pstore: inode: Use cleanup.h for struct pstore_private
Sergey Shtylyov (1):
pstore: ram_core: fix possible overflow in persistent_ram_init_ecc()
Weichen Chen (1):
pstore/ram: Fix crash when setting number of cpus to an odd number
fs/pstore/inode.c | 109 +++++++++++++++++++++------------------------------
fs/pstore/ram.c | 1 +
fs/pstore/ram_core.c | 2 +-
3 files changed, 46 insertions(+), 66 deletions(-)
--
Kees Cook
next reply other threads:[~2024-01-08 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 18:24 Kees Cook [this message]
2024-01-10 20:38 ` [GIT PULL] pstore updates for v6.8-rc1 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=202401081022.31D251086@keescook \
--to=keescook@chromium.org \
--cc=gpiccoli@igalia.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=s.shtylyov@omp.ru \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=weichen.chen@mediatek.com \
/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