mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: akpm@linux-foundation.org
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, mingo@redhat.com,
	LKML <linux-kernel@vger.kernel.org>,
	Ulrich Obergfell <uobergfe@redhat.com>,
	Andrew Jones <drjones@redhat.com>,
	Don Zickus <dzickus@redhat.com>
Subject: [PATCH 3/5] watchdog: fix print-once on enable
Date: Mon, 11 Aug 2014 10:49:25 -0400	[thread overview]
Message-ID: <1407768567-171794-4-git-send-email-dzickus@redhat.com> (raw)
In-Reply-To: <1407768567-171794-1-git-send-email-dzickus@redhat.com>

From: Ulrich Obergfell <uobergfe@redhat.com>

This patch avoids printing the message 'enabled on all CPUs, ...'
multiple times. For example, the issue can occur in the following
scenario:

1) watchdog_nmi_enable() fails to enable PMU counters and sets
   cpu0_err.

2) 'echo [0|1] > /proc/sys/kernel/nmi_watchdog' is executed to
   disable and re-enable the watchdog mechanism 'on the fly'.

3) If watchdog_nmi_enable() succeeds to enable PMU counters, each
   CPU will print the message because step1 left behind a non-zero
   cpu0_err.

   if (!IS_ERR(event)) {
       if (cpu == 0 || cpu0_err)
       pr_info("enabled on all CPUs, ...")

The patch avoids this by clearing cpu0_err in watchdog_nmi_disable().

Signed-off-by: Ulrich Obergfell <uobergfe@redhat.com>
Signed-off-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
---
 kernel/watchdog.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 6d0a891..0838685 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -522,6 +522,9 @@ static void watchdog_nmi_disable(unsigned int cpu)
 		/* should be in cleanup, but blocks oprofile */
 		perf_event_release_kernel(event);
 	}
+	if (cpu == 0)
+		/* watchdog_nmi_enable() expects this to be zero initially. */
+		cpu0_err = 0;
 	return;
 }
 #else
-- 
1.7.1


  parent reply	other threads:[~2014-08-11 14:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 14:49 [PATCH 0/5] watchdog: various fixes Don Zickus
2014-08-11 14:49 ` [PATCH 1/5] watchdog: remove unnecessary head files Don Zickus
2014-08-18 18:03   ` [tip:perf/watchdog] watchdog: Remove unnecessary header files tip-bot for chai wen
2014-08-11 14:49 ` [PATCH 2/5] softlockup: make detector be aware of task switch of processes hogging cpu Don Zickus
2014-08-18  9:03   ` Ingo Molnar
2014-08-18 15:06     ` Don Zickus
2014-08-18 18:01       ` Ingo Molnar
2014-08-18 18:43         ` Don Zickus
2014-08-18 19:02           ` Ingo Molnar
2014-08-18 20:38             ` Don Zickus
2014-08-19  1:36               ` Chai Wen
2014-08-21  1:37                 ` Chai Wen
2014-08-21  2:30                   ` Don Zickus
2014-08-21  5:42                     ` [PATCH] " chai wen
2014-08-22  1:12                       ` Chai Wen
2014-08-22  1:58                       ` Don Zickus
2014-08-26 12:51                         ` Chai Wen
2014-08-26 14:22                           ` Don Zickus
2014-08-27  1:33                             ` Chai Wen
2014-08-11 14:49 ` Don Zickus [this message]
2014-08-18  9:05   ` [PATCH 3/5] watchdog: fix print-once on enable Ingo Molnar
2014-08-18  9:07   ` Ingo Molnar
2014-08-18 15:07     ` Don Zickus
2014-08-18 18:03   ` [tip:perf/watchdog] watchdog: Fix " tip-bot for Ulrich Obergfell
2014-08-11 14:49 ` [PATCH 4/5] watchdog: control hard lockup detection default Don Zickus
2014-08-18  9:12   ` Ingo Molnar
2014-08-18 15:07     ` Don Zickus
2014-08-18  9:16   ` Ingo Molnar
2014-08-18 10:44     ` Ulrich Obergfell
2014-08-18 15:17     ` Don Zickus
2014-08-18 18:07       ` Ingo Molnar
2014-08-18 18:53         ` Don Zickus
2014-08-18 19:00           ` Ingo Molnar
2014-08-11 14:49 ` [PATCH 5/5] kvm: ensure hard lockup detection is disabled by default Don Zickus

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=1407768567-171794-4-git-send-email-dzickus@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --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

all inboxes | Powered by JetHome®