From: Don Zickus <dzickus@redhat.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Luck, Tony (tony.luck@intel.com)" <tony.luck@intel.com>,
"ccross@android.com" <ccross@android.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"cbouatmailru@gmail.com" <cbouatmailru@gmail.com>,
Satoru Moriya <satoru.moriya@hds.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>
Subject: Re: [PATCH v3 0/2] pstore,efi_pstore: Avoid deadlock in non-blocking paths
Date: Thu, 20 Dec 2012 14:09:23 -0500 [thread overview]
Message-ID: <20121220190923.GP88797@redhat.com> (raw)
In-Reply-To: <A5ED84D3BB3A384992CBB9C77DEDA4D414A2A03B@USINDEM103.corp.hds.com>
On Thu, Dec 20, 2012 at 03:11:14PM +0000, Seiji Aguchi wrote:
> Changelog
> v2 -> v3
> - Merge modifications of pstore part in 2/2 to 1/2.
> - Rename pstore_is_non_blocking_path() to pstore_cannot_block_path().
>
> v1 -> v2
> - Erase a logic checking the number of online cpus.
> - Create a patchset to fix deadlocking issue in both pstore filesystem and
> efi_pstore driver.
> - Introduce a function, is_non_blocking_path(), to check if pstore
> is in panic and emergency-restart paths (PATCH 1/2)
> - Avoid efi_pstore_driver is blocked in non-blocking paths
> such as nmi, panic and emergency-restart paths (PATCH 2/2)
>
> [Issue]
>
> There are some paths in kernel which shouldn't be blocked,
> like NMI, panic case after stopping cpus, emergency-restart.
I am ok with it.
Acked-by: Don Zickus <dzickus@redhat.com>
next prev parent reply other threads:[~2012-12-20 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 15:11 [PATCH v3 0/2] pstore,efi_pstore: Avoid deadlock in non-blocking paths Seiji Aguchi
2012-12-20 19:09 ` Don Zickus [this message]
2012-12-21 23:27 ` Seiji Aguchi
2012-12-21 23:37 ` Anton Vorontsov
2013-01-05 0:01 ` Seiji Aguchi
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=20121220190923.GP88797@redhat.com \
--to=dzickus@redhat.com \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).