lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fUs7WPQ1U-iXzZQDwa5Bm0Fg11Riw20AFnDDOScoY6BnA@mail.gmail.com>
Date: Mon, 15 Sep 2025 19:50:15 -0700
From: Ian Rogers <irogers@...gle.com>
To: Jinchao Wang <wangjinchao600@...il.com>
Cc: Doug Anderson <dianders@...omium.org>, Peter Zijlstra <peterz@...radead.org>, 
	Will Deacon <will@...nel.org>, Yunhui Cui <cuiyunhui@...edance.com>, akpm@...ux-foundation.org, 
	catalin.marinas@....com, maddy@...ux.ibm.com, mpe@...erman.id.au, 
	npiggin@...il.com, christophe.leroy@...roup.eu, tglx@...utronix.de, 
	mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com, 
	acme@...nel.org, namhyung@...nel.org, mark.rutland@....com, 
	alexander.shishkin@...ux.intel.com, jolsa@...nel.org, adrian.hunter@...el.com, 
	kan.liang@...ux.intel.com, kees@...nel.org, masahiroy@...nel.org, 
	aliceryhl@...gle.com, ojeda@...nel.org, thomas.weissschuh@...utronix.de, 
	xur@...gle.com, ruanjinjie@...wei.com, gshan@...hat.com, maz@...nel.org, 
	suzuki.poulose@....com, zhanjie9@...ilicon.com, yangyicong@...ilicon.com, 
	gautam@...ux.ibm.com, arnd@...db.de, zhao.xichao@...o.com, rppt@...nel.org, 
	lihuafei1@...wei.com, coxu@...hat.com, jpoimboe@...nel.org, 
	yaozhenguo1@...il.com, luogengkun@...weicloud.com, max.kellermann@...os.com, 
	tj@...nel.org, yury.norov@...il.com, thorsten.blum@...ux.dev, x86@...nel.org, 
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
	linuxppc-dev@...ts.ozlabs.org, linux-perf-users@...r.kernel.org
Subject: Re: [PATCH] watchdog: remove HARDLOCKUP_DETECTOR_PERF

On Mon, Sep 15, 2025 at 6:47 PM Jinchao Wang <wangjinchao600@...il.com> wrote:
> Should we support both modularization and changing the backend after
> boot, so that the user has the choice?

Having both together and then being able to choose one or the other
sounds like the ideal solution. An issue is that
/proc/sys/kernel/nmi_watchdog is used to dynamically enable/disable
both watchdogs and presumably renaming it for the buddy could cause
issues in user code.

There can be unexpected consequences of the buddy watchdog, as the NMI
perf event goes away there can be extra cost in setting up the first
event such as allocating buffers for the PMU. While enabling the NMI
watchdog to avoid this cost is kind of odd, I think users would be
glad of a workaround for what may be perceived as a regression.

Thanks,
Ian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ