From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 37436C388F9 for ; Fri, 23 Oct 2020 11:50:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CF26120EDD for ; Fri, 23 Oct 2020 11:50:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b="VhPvxGOC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S463213AbgJWLuB (ORCPT ); Fri, 23 Oct 2020 07:50:01 -0400 Received: from mx2.suse.de ([195.135.220.15]:55486 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S463205AbgJWLuA (ORCPT ); Fri, 23 Oct 2020 07:50:00 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1603453799; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=9AfaYkVLSY802vzN1LJgcu333YmY7HCYO1P84FAMi/c=; b=VhPvxGOCKGQS4yA7Fk0Kl6fSkFlLXWwjBdCv2Y1vyqBjIFLtQrXRJZueUokKs2ZZ9mkwQD msftKzV9SVTHY0X4ubAGAOvLyGd/s0SriHHK5gLceSyz11jm4bRZw/0O0HMqRyTuRnBOpq Vy3+v4ISg/urQrV6dHVSXmf8zgRqrBo= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 6A121ACBF; Fri, 23 Oct 2020 11:49:59 +0000 (UTC) Date: Fri, 23 Oct 2020 13:49:58 +0200 From: Petr Mladek To: John Ogness Cc: Guenter Roeck , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Shreyas Joshi , shreyasjoshi15@gmail.com, Greg Kroah-Hartman , Sergey Senozhatsky , linux-kernel@vger.kernel.org Subject: Re: [RFC 1/2] printk: Add kernel parameter: mute_console Message-ID: <20201023114958.GE32486@alley> References: <20201022114228.9098-1-pmladek@suse.com> <20201022114228.9098-2-pmladek@suse.com> <87a6wez9s4.fsf@jogness.linutronix.de> <5a30b3e8-c2c3-ceae-517e-c93fb2c3118f@roeck-us.net> <877driz50k.fsf@jogness.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877driz50k.fsf@jogness.linutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 2020-10-22 16:59:15, John Ogness wrote: > On 2020-10-22, Guenter Roeck wrote: > > The whole point of the exercise is to disable all consoles, including > > default ones which are not explicitly specified on the command line. > > In that case I think specifying something like: > > console=null > > makes that most sense. I think implementing a "null console" driver > would be quite simple. Then there would be no need for special handling > in the printk subsystem. Heh, it actually already exists and has been created for exactly this purpose, see the commit 3117ff13f104e98b05b6 ("tty: Add NULL TTY driver"). Regarding the interface: + console=null or console= is OK when people do not want consoles at all + mute_console (or another extra parameter) would be needed if people wanted to have login console. It is true that nobody asked for the login support. So, the null console should be enough for now. Best Regards, Petr