summaryrefslogtreecommitdiffstats
path: root/kernel/locking/rwsem.c
diff options
context:
space:
mode:
authorThierry Reding <treding@nvidia.com>2016-01-15 16:58:21 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2016-01-16 11:17:25 -0800
commit81cc26f2bd11ba4421a17a2d5cebe4bba206c239 (patch)
tree7236a686e7414995d926689247ae78f04a3c8163 /kernel/locking/rwsem.c
parent979559362516bb0f5424505c607210ac054e30ae (diff)
downloadtalos-obmc-linux-81cc26f2bd11ba4421a17a2d5cebe4bba206c239.tar.gz
talos-obmc-linux-81cc26f2bd11ba4421a17a2d5cebe4bba206c239.zip
printk: only unregister boot consoles when necessary
Boot consoles are typically replaced by proper consoles during the boot process. This can be problematic if the boot console data is part of the init section that is reclaimed late during boot. If the proper console does not register before this point in time, the boot console will need to be removed (so that the freed memory is not accessed), leaving the system without output for some time. There are various reasons why the proper console may not register early enough, such as deferred probe or the driver being a loadable module. If that happens, there is some amount of time where no console messages are visible to the user, which in turn can mean that they won't see crashes or other potentially useful information. To avoid this situation, only remove the boot console when it resides in the init section. Code exists to replace the boot console by the proper console when it is registered, keeping a seamless transition between the boot and proper consoles. Signed-off-by: Thierry Reding <treding@nvidia.com> Cc: Arnd Bergmann <arnd@arndb.de> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Joe Perches <joe@perches.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/locking/rwsem.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud