All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.com>
To: Toshi Kani <toshi.kani@hp.com>,
	wim@iguana.be, linux-watchdog@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, thomas.mingarelli@hp.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] hpwdt: Fix kdump issue in hpwdt
Date: Mon, 27 Aug 2012 21:22:27 +0200	[thread overview]
Message-ID: <20120827192227.GJ18709@suse.de> (raw)
In-Reply-To: <1346093544-12007-1-git-send-email-toshi.kani@hp.com>

On 2012-08-27T12:52:24, Toshi Kani <toshi.kani@hp.com> wrote:

> kdump can be interrupted by watchdog timer when the timer is left
> activated on the crash kernel. Changed the hpwdt driver to disable
> watchdog timer at boot-time. This assures that watchdog timer is
> disabled until /dev/watchdog is opened, and prevents watchdog timer
> to be left running on the crash kernel.

How does this protect against the system hanging again in the crash
kernel, or possibly hardware caches to flush more data to shared
storage?

(I'm asking from the perspective of the hpwdt being used as a fencing
mechanism in a cluster setting.)

Or is the argument that it's "very unlikely" that a system in such a
state would not make it far enough into the crash kernel?


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Lars Marowsky-Bree <lmb@suse.com>
To: Toshi Kani <toshi.kani@hp.com>,
	wim@iguana.be, linux-watchdog@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, thomas.mingarelli@hp.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] hpwdt: Fix kdump issue in hpwdt
Date: Mon, 27 Aug 2012 21:22:27 +0200	[thread overview]
Message-ID: <20120827192227.GJ18709@suse.de> (raw)
In-Reply-To: <1346093544-12007-1-git-send-email-toshi.kani@hp.com>

On 2012-08-27T12:52:24, Toshi Kani <toshi.kani@hp.com> wrote:

> kdump can be interrupted by watchdog timer when the timer is left
> activated on the crash kernel. Changed the hpwdt driver to disable
> watchdog timer at boot-time. This assures that watchdog timer is
> disabled until /dev/watchdog is opened, and prevents watchdog timer
> to be left running on the crash kernel.

How does this protect against the system hanging again in the crash
kernel, or possibly hardware caches to flush more data to shared
storage?

(I'm asking from the perspective of the hpwdt being used as a fencing
mechanism in a cluster setting.)

Or is the argument that it's "very unlikely" that a system in such a
state would not make it far enough into the crash kernel?


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde


  parent reply	other threads:[~2012-08-27 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 18:52 [PATCH] hpwdt: Fix kdump issue in hpwdt Toshi Kani
2012-08-27 18:59 ` Mingarelli, Thomas
2012-08-27 19:22 ` Lars Marowsky-Bree [this message]
2012-08-27 19:22   ` Lars Marowsky-Bree
2012-08-27 19:57   ` Mingarelli, Thomas
2012-08-27 20:44     ` Toshi Kani
2012-09-10 18:48 ` Wim Van Sebroeck
2012-09-10 18:48   ` Toshi Kani

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=20120827192227.GJ18709@suse.de \
    --to=lmb@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=thomas.mingarelli@hp.com \
    --cc=toshi.kani@hp.com \
    --cc=wim@iguana.be \
    /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.