From: Matt Fleming <matt@console-pimps.org>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"Luck, Tony (tony.luck@intel.com)" <tony.luck@intel.com>,
"mikew@google.com" <mikew@google.com>,
"cbouatmailru@gmail.com" <cbouatmailru@gmail.com>,
"dzickus@redhat.com" <dzickus@redhat.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [PATCH v5 -next 2/2]efi_pstore: Introducing workqueue updating sysfs entries
Date: Sat, 09 Feb 2013 20:12:35 +0000 [thread overview]
Message-ID: <1360440755.7515.322.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <A5ED84D3BB3A384992CBB9C77DEDA4D414A541C8@USINDEM103.corp.hds.com>
On Thu, 2013-01-24 at 00:41 +0000, Seiji Aguchi wrote:
> [Problem]
> efi_pstore creates sysfs entries, which enable users to access to NVRAM,
> in a write callback. If a kernel panic happens in an interrupt context,
> it may fail because it could sleep due to dynamic memory allocations during
> creating sysfs entries.
>
> [Patch Description]
> This patch removes sysfs operations from a write callback by introducing
> a workqueue updating sysfs entries which is scheduled after the write
> callback is called.
>
> Also, the workqueue is kicked in a just oops case.
> A system will go down in other cases such as panic, clean shutdown and emergency
> restart. And we don't need to create sysfs entries because there is no chance for
> users to access to them.
>
> efi_pstore will be robust against a kernel panic in an interrupt context with this patch.
>
> Signed-off-by: Seiji Aguchi <seiji.aguchi@hds.com>
> ---
> drivers/firmware/efivars.c | 85 +++++++++++++++++++++++++++++++++++++++++---
> include/linux/efi.h | 3 +-
> 2 files changed, 82 insertions(+), 6 deletions(-)
Acked-by: Matt Fleming <matt.fleming@intel.com>
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2013-02-09 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 0:41 Seiji Aguchi
2013-02-09 20:12 ` Matt Fleming [this message]
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=1360440755.7515.322.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt@console-pimps.org \
--cc=cbouatmailru@gmail.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=dzickus@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=tony.luck@intel.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®