linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Norbert Warmuth <nwarmuth@t-online.de>,
	Joseph Salisbury <joseph.salisbury@canonical.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RESEND][PATCH v3] watchdog: Fix disable/enable regression
Date: Thu, 20 Dec 2012 14:17:53 -0500	[thread overview]
Message-ID: <20121220191752.GR88797@redhat.com> (raw)
In-Reply-To: <87zk1967jn.fsf@nemi.mork.no>

On Wed, Dec 19, 2012 at 10:44:44PM +0100, Bjørn Mork wrote:
> Bjørn Mork <bjorn@mork.no> writes:
> > Don Zickus <dzickus@redhat.com> writes:
> >
> >> What about the opposite cases?  
> >> nmi_watchdog=1
> >> echo 1 > /sys/devices/system/cpu/cpu1/online
> >
> > I don't see why not. But verifying it would be nice.  I thought that it
> > would be a simple thing to test using qemu-kvm, but it seems that the
> > CPU hotplugging support there isn't quite ready. The guest just dies
> > with "Assertion `bus->allow_hotplug' failed."
> >
> > I'll go digging for alternatives, but if anyone else could verify this
> > then I'd appreciate it.
> 
> I just realized that you might not really want/need hotplugging, but
> just booting with some cores initially offline?

Actually, I did a poor job explaining myself but your previous email
answered my question.

The original problem was that hrtimer_cancel was being called on an
un-initialized object.  I was wondering what happens if watchdog_enable
was called multiple times, would it re-initialize a new object causing a
memory leak?

But as you pointed out that couldn't happen.

So I am fine with your changes.  Thanks for the initial and follow up
testing.

Acked-by: Don Zickus <dzickus@redhat.com>

      reply	other threads:[~2012-12-20 19:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14  9:33 Bisected oops regression between v3.7-rc8 and v3.7: nmi_watchdog Bjørn Mork
2012-12-14  9:34 ` [PATCH] Revert "watchdog: Fix CPU hotplug regression" Bjørn Mork
2012-12-14 13:44 ` [PATCH v2] watchdog: Fix disable/enable regression Bjørn Mork
2012-12-16 19:41 ` Bisected oops regression between v3.7-rc8 and v3.7: nmi_watchdog Maciej Rutecki
2012-12-18  8:13 ` [regression][PATCH v3] watchdog: Fix disable/enable regression Bjørn Mork
2012-12-19 19:51 ` [RESEND][PATCH " Bjørn Mork
2012-12-19 20:13   ` Don Zickus
2012-12-19 21:17     ` Bjørn Mork
2012-12-19 21:44       ` Bjørn Mork
2012-12-20 19:17         ` Don Zickus [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=20121220191752.GR88797@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bjorn@mork.no \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nwarmuth@t-online.de \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).