From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] pstore fix for v4.10-rc8
Date: Thu, 9 Feb 2017 11:56:46 -0800 [thread overview]
Message-ID: <20170209195646.GA39738@beast> (raw)
Hi,
This pstore regression was just noticed. If I'm too late, this can land
in v4.11 and -stable, but if the fix window is still open for v4.10, I'd
love to see this fix pulled for v4.10.
Thanks!
-Kees
The following changes since commit d966564fcdc19e13eb6ba1fbe6b8101070339c3d:
Revert "x86/ioapic: Restore IO-APIC irq_chip retrigger callback" (2017-02-08 18:08:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v4.10-rc8
for you to fetch changes up to 8672aed7bd865774257efd40929702759a869329:
pstore: don't OOPS when there are no ftrace zones (2017-02-09 11:49:49 -0800)
----------------------------------------------------------------
Fix pstore regression (boot Oops) when ftrace disabled, from Brian Norris.
----------------------------------------------------------------
Brian Norris (1):
pstore: don't OOPS when there are no ftrace zones
fs/pstore/ram.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Kees Cook
Pixel Security
next reply other threads:[~2017-02-09 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 19:56 Kees Cook [this message]
2017-02-09 20:52 ` [PATCH] ARM: multi_v7_defconfig: enable pstore configs Brian Norris
2017-02-09 20:52 ` Brian Norris
2017-02-16 16:22 ` Arnd Bergmann
2017-02-16 16:22 ` Arnd Bergmann
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=20170209195646.GA39738@beast \
--to=keescook@chromium.org \
--cc=briannorris@chromium.org \
--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.