Re: [PATCH 2/3] clear_warn_once: bind a timer to written reset value

2020-11-30 Thread Steven Rostedt
On Mon, 30 Nov 2020 12:17:59 -0500 Paul Gortmaker wrote: > > Anyway, would there ever be a need to have it cleared in less than 1 minute > > intervals? > > I don't think so - as I said in another follow up from last week: > > https://lore.kernel.org/lkml/20201127174316.ga11...@windriver.com/

Re: [PATCH 2/3] clear_warn_once: bind a timer to written reset value

2020-11-30 Thread Paul Gortmaker
[Re: [PATCH 2/3] clear_warn_once: bind a timer to written reset value] On 30/11/2020 (Mon 11:20) Steven Rostedt wrote: > On Thu, 26 Nov 2020 01:30:28 -0500 > Paul Gortmaker wrote: > > > +++ b/Documentation/admin-guide/clearing-warn-once.rst > > @@ -7,3 +7,12 @@ echo

Re: [PATCH 2/3] clear_warn_once: bind a timer to written reset value

2020-11-30 Thread Steven Rostedt
On Thu, 26 Nov 2020 01:30:28 -0500 Paul Gortmaker wrote: > +++ b/Documentation/admin-guide/clearing-warn-once.rst > @@ -7,3 +7,12 @@ echo 1 > /sys/kernel/debug/clear_warn_once > > clears the state and allows the warnings to print once again. > This can be useful after test suite runs to repro

[PATCH 2/3] clear_warn_once: bind a timer to written reset value

2020-11-25 Thread Paul Gortmaker
Existing documentation has a write of "1" to clear/reset all the WARN_ONCE and similar to the as-booted state, so they can possibly be re-triggered again during debugging/testing. But having them auto-reset once a day, or once a week, might shed valuable information to a sysadmin on what the syste