public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: akpm@linux-foundation.org, keescook@chromium.org,
	longman@redhat.com, mingo@kernel.org, mm-commits@vger.kernel.org,
	rppt@linux.ibm.com, peterz@infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: + watchdog-fix-possible-soft-lockup-warning-at-bootup-v2.patch added to -mm tree
Date: Thu, 16 Jan 2020 12:55:49 +0100	[thread overview]
Message-ID: <878sm7wr7e.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200107233656.GS5UK5wEy%akpm@linux-foundation.org>

akpm@linux-foundation.org writes:

> ------------------------------------------------------
> From: Waiman Long <longman@redhat.com>
> Subject: watchdog: Fix possible soft lockup warning at bootup

Completely empty changelog without any justification for this change.

> Link: http://lkml.kernel.org/r/20200103151032.19590-1-longman@redhat.com
> Signed-off-by: Waiman Long <longman@redhat.com>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Mike Rapoport <rppt@linux.ibm.com>
> Cc: Kees Cook <keescook@chromium.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
>  kernel/watchdog.c |    4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> --- a/kernel/watchdog.c~watchdog-fix-possible-soft-lockup-warning-at-bootup-v2
> +++ a/kernel/watchdog.c
> @@ -496,9 +496,7 @@ static void watchdog_enable(unsigned int
>  		      HRTIMER_MODE_REL_PINNED_HARD);
>  
>  	/* Initialize timestamp */
> -	if (system_state != SYSTEM_BOOTING)
> -		__touch_watchdog();
> -
> +	__touch_watchdog();
>  	/* Enable the perf event */
>  	if (watchdog_enabled & NMI_WATCHDOG_ENABLED)
>  		watchdog_nmi_enable(cpu);
> _
>
> Patches currently in -mm which might be from longman@redhat.com are
>
> watchdog-fix-possible-soft-lockup-warning-at-bootup.patch
> watchdog-fix-possible-soft-lockup-warning-at-bootup-v2.patch

Please drop both. The initial one just papers over timer interrupt loss
and weakens debugging. That V2 thing is just fixing up the wreckage
introduced in the initial one.

Thanks,

        tglx

       reply	other threads:[~2020-01-16 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200107233656.GS5UK5wEy%akpm@linux-foundation.org>
2020-01-16 11:55 ` Thomas Gleixner [this message]
2020-01-16 23:53   ` + watchdog-fix-possible-soft-lockup-warning-at-bootup-v2.patch added to -mm tree Andrew Morton

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=878sm7wr7e.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rppt@linux.ibm.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