From: Hedi Berriche <hedi.berriche@hpe.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Hedi Berriche <hedi.berriche@hpe.com>,
Borislav Petkov <bp@suse.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Russ Anderson <rja@hpe.com>, Dimitri Sivanich <sivanich@hpe.com>,
Steve Wahl <steve.wahl@hpe.com>,
Mike Travis <mike.travis@hpe.com>,
Andy Shevchenko <andy@infradead.org>,
Bhupesh Sharma <bhsharma@redhat.com>,
Darren Hart <dvhart@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
linux-efi <linux-efi@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, x86-ml <x86@kernel.org>
Subject: Please revert 7212e37cbdf9 from 4.4-stable
Date: Mon, 11 Mar 2019 13:48:14 +0000 [thread overview]
Message-ID: <20190311134814.GC30367@sarge.linuxathome.me> (raw)
Hi Greg,
Could you please revert
7212e37cbdf9 x86/platform/UV: Use efi_runtime_lock to serialise BIOS calls
from 4.4-stable?
In 4.4-stable efi_runtime_lock as defined in drivers/firmware/efi/runtime-wrappers.c
is a spinlock (given it predates commit dce48e351c0d) and commit
f331e766c4be x86/platform/UV: Use efi_runtime_lock to serialise BIOS calls
which 7212e37cbdf9 is a backport of, needs it to be a semaphore.
Cheers,
Hedi.
--
Be careful of reading health books, you might die of a misprint.
-- Mark Twain
next reply other threads:[~2019-03-11 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 13:48 Hedi Berriche [this message]
2019-03-12 0:29 ` Please revert 7212e37cbdf9 from 4.4-stable Sasha Levin
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=20190311134814.GC30367@sarge.linuxathome.me \
--to=hedi.berriche@hpe.com \
--cc=andy@infradead.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhsharma@redhat.com \
--cc=bp@suse.de \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rja@hpe.com \
--cc=sivanich@hpe.com \
--cc=stable@vger.kernel.org \
--cc=steve.wahl@hpe.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).