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;
Date:   Tue, 19 Jul 2022 13:11:25 +0100
From:   Chris Down <chris@chrisdown.name>
To:     Petr Mladek <pmladek@suse.com>
Cc:     linux-kernel@vger.kernel.org,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Sergey Senozhatsky <senozhatsky@chromium.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        John Ogness <john.ogness@linutronix.de>,
        Geert Uytterhoeven <geert@linux-m68k.org>, kernel-team@fb.com
Subject: Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each
 console to have its own loglevel
Message-ID: <Ytafbe6jGQ9sW7HG@chrisdown.name>
References: <YoeQLxhDeIk4VSmx@chrisdown.name>
 <YshL2M8VdIEONDdc@alley>
 <Ys7bb8+/G0iMWfzb@chrisdown.name>
 <20220714154452.GB24338@pathway.suse.cz>
 <20220715124935.GE2737@pathway.suse.cz>
 <YtFk/3XA8dsaTu/c@chrisdown.name>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <YtFk/3XA8dsaTu/c@chrisdown.name>
User-Agent: Mutt/2.2.6 (2022-06-05)
Precedence: bulk

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.