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: Tue, 19 Jul 2022 13:11:25 +0100 From: Chris Down <chris@...isdown.name> To: Petr Mladek <pmladek@...e.com> Cc: linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Sergey Senozhatsky <senozhatsky@...omium.org>, Steven Rostedt <rostedt@...dmis.org>, John Ogness <john.ogness@...utronix.de>, Geert Uytterhoeven <geert@...ux-m68k.org>, kernel-team@...com Subject: Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each console to have its own loglevel Chris Down writes: >Ok, I will incorporate the EINVAL return for sysctl in a separate >patch first, and then add the new sysfs one to the existing changes >for v3. :-) Thinking more about this, I will probably not change the existing kernel.printk semantics to return EINVAL, since it could silently(ish) cause regressions for existing misconfigured systems on boot. I'll just add the clamps to the new controls.
Powered by blists - more mailing lists