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
| ||
|
Date: Mon, 30 Nov 2020 11:24:48 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Petr Mladek <pmladek@...e.com> Cc: Paul Gortmaker <paul.gortmaker@...driver.com>, linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, John Ogness <john.ogness@...utronix.de> Subject: Re: [PATCH 0/3] clear_warn_once: add timed interval resetting On Fri, 27 Nov 2020 17:13:52 +0100 Petr Mladek <pmladek@...e.com> wrote: > I do not know. Maybe I am just too paranoid today. Anyway, there > are other possibilities: This is another reason I think the resolution should be in minutes and not seconds. It would be less of an issue if it could dump all warnings only once a minute than once every two seconds. > > + Move clear_warn_once from debugfs to a location that is always > available. For example, into /proc I was thinking of /proc/sys/ as well. -- Steve
Powered by blists - more mailing lists