From: Don Zickus <dzickus@redhat.com>
To: Ulrich Obergfell <uobergfe@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Michal Hocko <mhocko@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Stephane Eranian <eranian@google.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-pm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: suspend regression in 4.1-rc1
Date: Mon, 18 May 2015 10:26:07 -0400 [thread overview]
Message-ID: <20150518142607.GL184517@redhat.com> (raw)
In-Reply-To: <309071648.615900.1431946606778.JavaMail.zimbra@redhat.com>
On Mon, May 18, 2015 at 06:56:46AM -0400, Ulrich Obergfell wrote:
>
> > There further appears to be a distinct lack of serialization between
> > setting and using watchdog_enabled, so perhaps we should wrap the
> > {en,dis}able_all() things in watchdog_proc_mutex.
>
> As I understand it, the {en,dis}able_all() functions are only called early
> at kernel startup, so I do not see how they could be racing with watchdog
> code that is executed in the context of write() system calls to parameters
> in /proc/sys/kernel. Please see also my earlier reply to Michal for further
> details: http://marc.info/?l=linux-pm&m=143194387208250&w=2
>
> Do we really need synchronization here?
As Peter said we have to focus on doing things correctly and not based on
what is currently.
During s2ram, I believe all the threads get parked and then unparked during
resume. I am wondering if the race happens there, threads get unparked and
stomp on each other when watchdog_nmi_enable_all() is called. (or vice
versa on the way down). I think during boot the cpu bring up is slow enough
that the race doesn't happen, but s2ram is alot quicker. My guess.
Cheers,
Don
>
> > This patch fixes a s2r failure reported by Michal; which I cannot
> > readily explain. But this does make the code internally consistent
> > again.
> >
> > Reported-and-tested-by: Michal Hocko <mhocko@suse.cz>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > ---
> > kernel/watchdog.c | 20 +++++++++++++++-----
> > 1 file changed, 15 insertions(+), 5 deletions(-)
> >
> > diff --git a/kernel/watchdog.c b/kernel/watchdog.c
> > index 2316f50..506edcc5 100644
> > --- a/kernel/watchdog.c
> > +++ b/kernel/watchdog.c
> > @@ -41,6 +41,8 @@
> > #define NMI_WATCHDOG_ENABLED (1 << NMI_WATCHDOG_ENABLED_BIT)
> > #define SOFT_WATCHDOG_ENABLED (1 << SOFT_WATCHDOG_ENABLED_BIT)
> >
> > +static DEFINE_MUTEX(watchdog_proc_mutex);
> > +
> > #ifdef CONFIG_HARDLOCKUP_DETECTOR
> > static unsigned long __read_mostly watchdog_enabled = SOFT_WATCHDOG_ENABLED|NMI_WATCHDOG_ENABLED;
> > #else
> > @@ -608,26 +610,36 @@ void watchdog_nmi_enable_all(void)
> > {
> > int cpu;
> >
> > - if (!watchdog_user_enabled)
> > - return;
> > + mutex_lock(&watchdog_proc_mutex);
> > +
> > + if (!(watchdog_enabled & NMI_WATCHDOG_ENABLED))
> > + goto unlock;
> >
> > get_online_cpus();
> > for_each_online_cpu(cpu)
> > watchdog_nmi_enable(cpu);
> > put_online_cpus();
> > +
> > +unlock:
> > + mutex_lock(&watchdog_proc_mutex);
> > }
> >
> > void watchdog_nmi_disable_all(void)
> > {
> > int cpu;
> >
> > + mutex_lock(&watchdog_proc_mutex);
> > +
> > if (!watchdog_running)
> > - return;
> > + goto unlock;
> >
> > get_online_cpus();
> > for_each_online_cpu(cpu)
> > watchdog_nmi_disable(cpu);
> > put_online_cpus();
> > +
> > +unlock:
> > + mutex_unlock(&watchdog_proc_mutex);
> > }
> > #else
> > static int watchdog_nmi_enable(unsigned int cpu) { return 0; }
> > @@ -744,8 +756,6 @@ static int proc_watchdog_update(void)
> >
> > }
> >
> > -static DEFINE_MUTEX(watchdog_proc_mutex);
> > -
> > /*
> > * common function for watchdog, nmi_watchdog and soft_watchdog parameter
> > *
next prev parent reply other threads:[~2015-05-18 14:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 18:50 Michal Hocko
2015-05-18 1:49 ` Sergey Senozhatsky
2015-05-18 4:33 ` Linus Torvalds
2015-05-18 7:30 ` Peter Zijlstra
2015-05-18 8:41 ` Peter Zijlstra
2015-05-18 9:03 ` Michal Hocko
2015-05-18 9:31 ` Peter Zijlstra
2015-05-18 10:56 ` Ulrich Obergfell
2015-05-18 11:05 ` Peter Zijlstra
2015-05-18 12:13 ` Stephane Eranian
2015-05-18 14:26 ` Don Zickus [this message]
2015-05-18 14:41 ` Michal Hocko
2015-05-18 15:45 ` Don Zickus
2015-05-19 17:20 ` Michal Hocko
2015-05-18 14:20 ` Don Zickus
2015-05-18 17:10 ` Linus Torvalds
2015-05-19 7:12 ` Michal Hocko
2015-05-19 7:39 ` Peter Zijlstra
2015-05-18 10:10 ` Ulrich Obergfell
2015-05-18 10:51 ` Peter Zijlstra
2015-05-18 12:03 ` Michal Hocko
2015-05-18 5:18 ` Omar Sandoval
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=20150518142607.GL184517@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eranian@google.com \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=torvalds@linux-foundation.org \
--cc=ulf.hansson@linaro.org \
--cc=uobergfe@redhat.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
Powered by JetHome