[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1421328867.519739764.uwqo04hs@frv35.fwdcdn.com>
Date: Thu, 15 Jan 2015 16:34:38 +0200
From: Sergey Popov <popov_sergey@....net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org
Subject: [patch 1/1] init/main.c: prevent increase of console_loglevel by
'quiet' kernel parameter
From: Sergey Popov <popov_sergey@....net>
Prevent increase of console_loglevel by 'quiet'
'quiet' kernel option that follows the 'loglevel=N' should
not blindly overwrite console_loglevel, instead it should
respect and keep lower 'loglevel'.
Signed-off-by: Sergey Popov <popov_sergey@....net>
---
init/main.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
Some drivers tend to print error messages (ex: 'drm/i810 does not support SMP') to the console
that we at our company don't want to show to people. We use 'quiet' kernel option to hide kernel decompressing progress and other messages not related to printk. But to hide error messages from drivers we use 'loglevel=3' parameter as well. But when it's _before_ the quiet, then quiet overrides loglevel=3 and set it to be 4.
I think that's a bug, and here's simple solution for it. The only way to live without this patch is to pass 'loglevel=3' after the 'quiet'. This issue is known to the community, but everyone is using workaround (ex: https://wiki.archlinux.org/index.php/Silent_boot).
I had enough inspiration to dive into the linux code and fix it.
--
with best regards,
Sergey Popov
phone: +380687507707
skype: uazure
vk.com/uazure
fb.com/uazure
Download attachment "sergey-popov-quiet-respects-loglevel.patch" of type "application/x-patch" (475 bytes)
Powered by blists - more mailing lists