From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Connor O'Brien <connoro@google.com>,
John Stultz <jstultz@google.com>,
Kees Cook <keescook@chromium.org>,
kernel-team@android.com, kernel test robot <lkp@intel.com>,
Luca Stefani <luca@osomprivacy.com>,
Midas Chien <midaschieh@google.com>,
Tony Luck <tony.luck@intel.com>, Wei Wang <wvw@google.com>
Subject: [GIT PULL] pstore updates for v6.2-rc1-fixes
Date: Fri, 23 Dec 2022 10:38:15 -0800 [thread overview]
Message-ID: <202212231038.955181AC@keescook> (raw)
Hi Linus,
Please pull these pstore fixes for v6.2-rc1.
Thanks!
-Kees
The following changes since commit e6b842741b4f39007215fd7e545cb55aa3d358a2:
pstore: Avoid kcore oops by vmap()ing with VM_IOREMAP (2022-12-05 16:15:09 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v6.2-rc1-fixes
for you to fetch changes up to beca3e311a49cd3c55a056096531737d7afa4361:
pstore: Properly assign mem_type property (2022-12-23 10:34:25 -0800)
----------------------------------------------------------------
pstore updates for v6.2-rc1-fixes
- Switch pmsg_lock to an rt_mutex to avoid priority inversion (John Stultz)
- Correctly assign mem_type property (Luca Stefani)
----------------------------------------------------------------
John Stultz (2):
pstore: Switch pmsg_lock to an rt_mutex to avoid priority inversion
pstore: Make sure CONFIG_PSTORE_PMSG selects CONFIG_RT_MUTEXES
Luca Stefani (1):
pstore: Properly assign mem_type property
fs/pstore/Kconfig | 1 +
fs/pstore/pmsg.c | 7 ++++---
fs/pstore/ram.c | 2 +-
3 files changed, 6 insertions(+), 4 deletions(-)
--
Kees Cook
next reply other threads:[~2022-12-23 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 18:38 Kees Cook [this message]
2022-12-23 20:08 ` 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=202212231038.955181AC@keescook \
--to=keescook@chromium.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=connoro@google.com \
--cc=jstultz@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luca@osomprivacy.com \
--cc=midaschieh@google.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=wvw@google.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
all inboxes | Powered by JetHome®