The commit 48021f98130880dd74 ("printk: handle blank console arguments passed in.") prevented crash caused by empty console= parameter value. Unfortunately, this value is widely used on Chromebooks to disable the console output. The above commit caused performance regression because the messages were pushed on slow console even though nobody was watching it. Use ttynull driver explicitly for console="" and console=null parameters. It has been created for exactly this purpose. It causes that preferred_console is set. As a result, ttySX and ttyX are not used as a fallback. And only ttynull console gets registered by default. It still allows to register other consoles either by additional console= parameters or SPCR. It prevents regression because it worked this way even before. Also it is a sane semantic. Preventing output on all consoles should be done another way, for example, by introducing mute_console parameter.
Unified · Split
| @@ -2189,8 +2189,15 @@ static int __init console_setup(char *str) · 2188 unmodified lines | ||
| 2189 | 2189 | char *s, *options, *brl_options = NULL; |
| 2190 | 2190 | int idx; |
| 2191 | 2191 | |
| 2192 | − if (str[0] == 0) | |
| 2192 | + /* | |
| 2193 | + * console="" or console=null have been suggested as a way to | |
| 2194 | + * disable console output. Use ttynull that has been created | |
| 2195 | + * for exacly this purpose. | |
| 2196 | + */ | |
| 2197 | + if (str[0] == 0 || strcmp(str, "null") == 0) { | |
| 2198 | + __add_preferred_console("ttynull", 0, NULL, NULL, true); | |
| 2193 | 2199 | return 1; |
| 2200 | + } | |
| 2194 | 2201 | |
| 2195 | 2202 | if (_braille_console_setup(&str, &brl_options)) |
| 2196 | 2203 | return 1; |