All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Ulrich Obergfell <uobergfe@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] watchdog: Fix watchdog_nmi_enable_all()
Date: Thu, 23 Apr 2015 09:19:49 -0400	[thread overview]
Message-ID: <20150423131949.GY98296@redhat.com> (raw)
In-Reply-To: <1728913539.5390910.1429777822876.JavaMail.zimbra@redhat.com>

On Thu, Apr 23, 2015 at 04:30:22AM -0400, Ulrich Obergfell wrote:
> > ----- Original Message -----
> > From: "Andrew Morton" <akpm@linux-foundation.org>
> > To: "Don Zickus" <dzickus@redhat.com>
> > Cc: "LKML" <linux-kernel@vger.kernel.org>, "Ulrich Obergfell" <uobergfe@redhat.com>
> > Sent: Wednesday, April 22, 2015 10:12:01 PM
> > Subject: Re: [PATCH] watchdog: Fix watchdog_nmi_enable_all()
> >
> > On Wed, 22 Apr 2015 10:47:49 -0400 Don Zickus <dzickus@redhat.com> wrote:
> >
> >> From: Ulrich Obergfell <uobergfe@redhat.com>
> >> 
> >> The 'watchdog_user_enabled' variable is only used as an 'interface'
> >> to the /proc/sys/kernel/watchdog parameter. The actual state of the
> >> watchdog is tracked by bits in the 'watchdog_enabled' variable. So,
> >> watchdog_nmi_enable_all() should check the NMI_WATCHDOG_ENABLED bit
> >> in 'watchdog_enabled'.
> >
> > What are the user-visible effects of the patch?  Please always include
> > this information when fixing a bug.
> 
> Andrew,
> 
> this patch has no user-visible effects. The issue that is addressed by this
> patch came up during the recent merges. It is related to:
> 
> 1) https://lkml.org/lkml/2015/2/5/624
> 2) http://lkml.kernel.org/r/1416251225-17721-12-git-send-email-eranian@google.com
> 
> Patch series 1) changes the way how the code in kernel/watchdog.c uses certain
> variables such as 'watchdog_user_enabled' and it also introduces a new variable
> 'watchdog_enabled' as described in:
> 
>    https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/kernel/watchdog.c?id=84d56e66b9b4a646f04ec30696ca1aeea5e654d5
> 
> This patch adjusts patch 2) which introduces watchdog_nmi_enable_all() to the
> new way how the code in kernel/watchdog.c should use 'watchdog_user_enabled'
> and 'watchdog_enabled'. Patch 2) is here:
> 
>   https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/kernel/watchdog.c?id=b3738d29323344da3017a91010530cf3a58590fc

Hi Andrew,

Sorry about that.  As Uli describes above, he pushed some patches to change
how the variable was used.  From the time his patches were posted to the
time they were committed, another patch popped in that was not updated to
use the new mechanism he patches created.

This patch just modifies Stephane's patch to reflect the changes Uli posted.

You are right, I did a poor job explaining that.  I hope things are clearer.

Do you want me to repost with an updated explaination?

Cheers,
Don

      reply	other threads:[~2015-04-23 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 14:47 [PATCH] watchdog: Fix watchdog_nmi_enable_all() Don Zickus
2015-04-22 20:12 ` Andrew Morton
2015-04-23  8:30   ` Ulrich Obergfell
2015-04-23 13:19     ` 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=20150423131949.GY98296@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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.