Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <bc4da863-dacb-66a7-133d-0e6e91e4477a@linux.alibaba.com>
Date:   Sun, 6 Aug 2023 10:52:57 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.13.0
Subject: Re: [PATCH] watchdog/hardlockup: set watchdog_hardlockup_warned to
 true as early as possible
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     dianders@chromium.org, pmladek@suse.com,
        linux-kernel@vger.kernel.org
References: <20230805160144.121875-1-liusong@linux.alibaba.com>
 <20230805101705.3a38ce9aacc924f1c9f0842b@linux-foundation.org>
From:   Liu Song <liusong@linux.alibaba.com>
In-Reply-To: <20230805101705.3a38ce9aacc924f1c9f0842b@linux-foundation.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk


在 2023/8/6 01:17, Andrew Morton 写道:
> When resending, please tell us some more about the effects of the
> change.  Presumably there are circumstances in which excess output is
> produced?  If so, describe these circumstances and the observed
> effects.

Hi,

I haven't found duplicate warnings in the real environment.

However, considering that when system occurs hard lockup is basically 
abnormal, it

seems more reasonable to set "watchdog_hardlockup_warned" to ture, 
rather than

waiting for all kinds of information to be printed.


Thanks