From: Li Zhong <zhong@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Paul Mackerras <paulus@samba.org>,
PowerPC email list <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [powerpc] init nvram_pstore_info's buf_lock
Date: Tue, 18 Nov 2014 14:12:38 +0800 [thread overview]
Message-ID: <1416291158.2327.11.camel@TP420> (raw)
In-Reply-To: <20141118043314.4517C14011D@ozlabs.org>
On 二, 2014-11-18 at 15:33 +1100, Michael Ellerman wrote:
> On Mon, 2014-17-11 at 02:52:30 UTC, Li Zhong wrote:
> > It seems nvram_pstore_info's buf_lock is not initialized before
> > registering, which causes some strange behavior when trying to obtain
> > the lock during kdump process.
>
> What kind of strange behaviour? Does it still work and just print a warning?
>
> It's static, so I'd expect it to be unlocked by default.
Yes, you are right. It still works.
I saw it on a UP configuration, noticed the console stopped for a couple
of seconds, then "lockup suspected" warning printed out, but then it
continued to run.
After some further checking, it seems working as designed for the UP
spinlock debug, from the comments in spinlock_up.h
* In the debug case, 1 means unlocked, 0 means locked. (the values
* are inverted, to catch initialization bugs)
So try lock fails, and lockup reported, but then arch_spin_lock()
passes.
Thanks, Zhong
>
> cheers
>
prev parent reply other threads:[~2014-11-18 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 2:52 [PATCH powerpc] init nvram_pstore_info's buf_lock Li Zhong
2014-11-18 4:33 ` [powerpc] " Michael Ellerman
2014-11-18 6:12 ` Li Zhong [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=1416291158.2327.11.camel@TP420 \
--to=zhong@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).