From: Don Zickus <dzickus@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Michal Hocko <mhocko@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Stephane Eranian <eranian@google.com>,
Ulrich Obergfell <uobergfe@redhat.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" <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:20:37 -0400 [thread overview]
Message-ID: <20150518142037.GK184517@redhat.com> (raw)
In-Reply-To: <20150518093150.GC21418@twins.programming.kicks-ass.net>
On Mon, May 18, 2015 at 11:31:50AM +0200, Peter Zijlstra wrote:
> On Mon, May 18, 2015 at 11:03:37AM +0200, Michal Hocko wrote:
> > This doesn't hang anymore. I've just had to move the mutex definition
> > up to make it compile. So feel free to add my
>
> I've also fixed a lock leak, see goto unlock :-)
>
> > Reported-and-tested-by: Michal Hocko <mhocko@suse.cz>
>
> *blink* that actually fixed it..
>
> That somewhat leaves me at a loss explaining how s2r was failing.
>
> ---
> Subject: watchdog: Fix merge 'conflict'
>
> Two watchdog changes that came through different trees had a non
> conflicting conflict, that is, one changed the semantics of a variable
> but no actual code conflict happened. So the merge appeared fine, but
> the resulting code did not behave as expected.
>
> Commit 195daf665a62 ("watchdog: enable the new user interface of the
> watchdog mechanism") changes the semantics of watchdog_user_enabled,
> which thereafter is only used by the functions introduced by
> b3738d293233 ("watchdog: Add watchdog enable/disable all functions").
>
> 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.
>
> This patch fixes a s2r failure reported by Michal; which I cannot
> readily explain. But this does make the code internally consistent
> again.
I agree with Peter's locking approach. We need to do better locking the
variables here. Poking around the code I see too many variables being
exposed sadly.
Thanks Peter!
Andrew, this patch can replace 'watchdog-fix-watchdog_nmi_enable_all.patch'
on your queue.
Acked-by: Don Zickus <dzickus@redhat.com>
>
> 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:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 18:50 suspend regression in 4.1-rc1 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
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 [this message]
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=20150518142037.GK184517@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.