From: Hans de Goede <hdegoede@redhat.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Make CONSOLE_LOGLEVEL_QUIET configurable
Date: Wed, 20 Jun 2018 15:43:09 +0200 [thread overview]
Message-ID: <ad4ecac7-e57b-b058-7179-54c5dd949745@redhat.com> (raw)
In-Reply-To: <20180620112436.GF444@jagdpanzerIV>
Hi,
On 20-06-18 13:24, Sergey Senozhatsky wrote:
> On (06/20/18 13:03), Petr Mladek wrote:
>>> This commit makes CONSOLE_LOGLEVEL_QUIET configurable.
>>>
>>> This for example will allow distros which want quiet to really mean quiet
>>> to set CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity
>>> then KERN_ERR (CRIT, ALERT, EMERG) get printed, avoiding an endless game
>>> of whack-a-mole silencing harmless error messages.
>>
>> I find it a bit confusing that "quiet" would mean something different
>> on different systems.
>
> Good that you brought this up. I had similar feelings but then the
> patch looked rather simple and I kinda agreed with it. If we can come
> up with alternative solution (you mentioned some) then it would be
> great.
I guess with my downstream hat on that we could live with silent,
but I would much prefer changing quiet, also so that we can lower
the firehose of mostly false-positive bugs coming in because of this.
Here is a short list from quick search which in no way is complete
(tip of the iceberg really):
1413342 - Linux 4.9.3: ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOU
1415853 - ACPI Error: Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-
1514937 - ACPI Error: AE_NOT_FOUND
1527870 - ACPI Error: [\_SB_.PCI0.SAT1] Namespace lookup failure, AE_NOT_FOUND
1552580 - ACPI Error: Method parse/execution failed
1553320 - Kernel errors at bootup -- system runs okay
1556967 - ACPI Error: [SMIC] Namespace lookup failure, AE_ALREADY_EXISTS
1582825 - ACPI Error: Method parse/execution failed
https://bugzilla.kernel.org/show_bug.cgi?id=109511
https://bugzilla.kernel.org/show_bug.cgi?id=194687
If we change quiet to filter these out, all of these will go away, if
we add a new silent option then only fresh installs will get the
new silent option and the benefit will be much reduced.
Besides that we would also need to make e.g. arch/x86/boot/edd.c
check for both quiet and silent and of course init/main.c and probably
others too, so form a code complexity pov the Kconfig way seems better too.
Regards,
Hans
next prev parent reply other threads:[~2018-06-20 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 11:57 Hans de Goede
2018-06-19 13:31 ` Steven Rostedt
2018-06-20 6:34 ` Sergey Senozhatsky
2018-06-20 11:03 ` Petr Mladek
2018-06-20 11:24 ` Sergey Senozhatsky
2018-06-20 13:43 ` Hans de Goede [this message]
2018-06-21 1:43 ` Sergey Senozhatsky
2018-06-20 13:37 ` Hans de Goede
2018-06-25 14:56 ` Petr Mladek
2018-06-20 14:07 ` Steven Rostedt
2018-06-20 14:18 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad4ecac7-e57b-b058-7179-54c5dd949745@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®