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 > _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
