reduce console_lock scope
Subsystems (19)
John Ogness
maintainerv5 cover reduce console_lock scope
This is v5 of a series to prepare for threaded/atomic printing. v4 is here [0]. This series focuses on reducing the scope of the BKL console_lock. It achieves this by switching to SRCU and a dedicated mutex for console list iteration and modification, respectively. The console_lock will no longer offer this protection.
Also, during the review of v2 it came to our attention that many console drivers are checking CON_ENABLED to see if they are registered. Because this flag can change without unregistering and because this flag does not represent an atomic point when an (un)registration process is complete, a new console_is_registered() function is introduced. This function uses the console_list_lock to synchronize with the (un)registration process to provide a reliable status.
All users of the console_lock for list iteration have been modified. For the call sites where the console_lock is still needed (for other reasons), comments are added to explain exactly why the console_lock is needed.
All users of CON_ENABLED for registration status have been modified to use console_is_registered(). Note that there are still users of CON_ENABLED, but this is for legitimate purposes about a registered console being able to print.
The base commit for this series is from Paul McKenney's RCU tree and provides an NMI-safe SRCU implementation [1]. Without the NMI-safe SRCU implementation, this series is not less safe than mainline. But we will need the NMI-safe SRCU implementation for atomic consoles anyway, so we might as well get it in now. Especially since it _does_ increase the reliability for mainline in the panic path.
Changes since v4:
printk:
- Introduce console_init_seq() to handle the now rather complex procedure to find an appropriate start sequence number for a new console upon registration.
- When registering a non-boot console and boot consoles are registered, try to flush all the consoles to get the next @seq value before falling back to use the @seq of the enabled boot console that is furthest behind.
- For console_force_preferred_locked(), make the console the head of the console list.
John Ogness
[0] https://lore.kernel.org/lkml/[email protected]
[1] https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/log/?h=srcunmisafe.2022.11.09a
John Ogness (38):
printk: Prepare for SRCU console list protection
printk: register_console: use "registered" for variable names
printk: move @seq initialization to helper
printk: fix setting first seq for consoles
um: kmsg_dump: only dump when no output console available
tty: serial: kgdboc: document console_lock usage
tty: tty_io: document console_lock usage
proc: consoles: document console_lock usage
printk: introduce console_list_lock
console: introduce wrappers to read/write console flags
um: kmsg_dumper: use srcu console list iterator
kdb: use srcu console list iterator
printk: console_flush_all: use srcu console list iterator
printk: __pr_flush: use srcu console list iterator
printk: console_is_usable: use console_srcu_read_flags
printk: console_unblank: use srcu console list iterator
printk: console_flush_on_panic: use srcu console list iterator
printk: console_device: use srcu console list iterator
console: introduce console_is_registered()
serial_core: replace uart_console_enabled() with
uart_console_registered()
tty: nfcon: use console_is_registered()
efi: earlycon: use console_is_registered()
tty: hvc: use console_is_registered()
tty: serial: earlycon: use console_is_registered()
tty: serial: pic32_uart: use console_is_registered()
tty: serial: samsung_tty: use console_is_registered()
tty: serial: xilinx_uartps: use console_is_registered()
usb: early: xhci-dbc: use console_is_registered()
netconsole: avoid CON_ENABLED misuse to track registration printk, xen: fbfront: create/use safe function for forcing preferred
tty: tty_io: use console_list_lock for list synchronization
proc: consoles: use console_list_lock for list iteration
tty: serial: kgdboc: use srcu console list iterator
tty: serial: kgdboc: use console_list_lock for list traversal
tty: serial: kgdboc: synchronize tty_find_polling_driver() and
register_console()
tty: serial: kgdboc: use console_list_lock to trap exit
printk: relieve console_lock of list synchronization duties
tty: serial: sh-sci: use setup() callback for early console
Thomas Gleixner (2):
serial: kgdboc: Lock console list in probe function
printk: Convert console_drivers list to hlist
.clang-format | 1 + arch/m68k/emu/nfcon.c | 9 +- arch/um/kernel/kmsg_dump.c | 24 +- drivers/firmware/efi/earlycon.c | 8 +- drivers/net/netconsole.c | 21 +- drivers/tty/hvc/hvc_console.c | 4 +- drivers/tty/serial/8250/8250_core.c | 2 +- drivers/tty/serial/earlycon.c | 4 +- drivers/tty/serial/kgdboc.c | 46 ++- drivers/tty/serial/pic32_uart.c | 4 +- drivers/tty/serial/samsung_tty.c | 2 +- drivers/tty/serial/serial_core.c | 14 +- drivers/tty/serial/sh-sci.c | 20 +- drivers/tty/serial/xilinx_uartps.c | 2 +- drivers/tty/tty_io.c | 18 +- drivers/usb/early/xhci-dbc.c | 2 +- drivers/video/fbdev/xen-fbfront.c | 12 +- fs/proc/consoles.c | 21 +- include/linux/console.h | 129 +++++++- include/linux/serial_core.h | 10 +- kernel/debug/kdb/kdb_io.c | 18 +- kernel/printk/printk.c | 493 +++++++++++++++++++++------- 22 files changed, 680 insertions(+), 184 deletions(-)
base-commit: f733615e39aa2d6ddeef33b7b2c9aa6a5a2c2785
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 1/40 serial: kgdboc: Lock console list in probe function
From: Thomas Gleixner <[email protected]>
Unprotected list walks are not necessarily safe.
--- drivers/tty/serial/kgdboc.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/tty/serial/kgdboc.c +2 -0
@@ -193,6 +193,7 @@ static int configure_kgdboc(void)if (!p) goto noconfig; +console_lock ();for_each_console (cons) {int idx; if (cons->device && cons->device(cons, &idx) == p &&
@@ -201,6 +202,7 @@ static int configure_kgdboc(void)break ; } } +console_unlock (); kgdb_tty_driver = p; kgdb_tty_line = tty_line;
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 2/40 printk: Convert console_drivers list to hlist
In reply to John OgnessFrom: Thomas Gleixner <[email protected]>
Replace the open coded single linked list with a hlist so a conversion to SRCU protected list walks can reuse the existing primitives.
--- fs/proc/consoles.c | 3 +- include/linux/console.h | 8 ++-- kernel/printk/printk.c | 101 ++++++++++++++++++++++------------------ 3 files changed, 62 insertions(+), 50 deletions(-)
fs/proc/consoles.c +2 -1
@@ -74,8 +74,9 @@ static void *c_start(struct seq_file *m, loff_t *pos)static void *c_next (struct seq_file *m,void *v,loff_t *pos) {struct console *con = v; + ++*pos; -return con->next; + return hlist_entry_safe(con->node.next, struct console, node); }static void c_stop (struct seq_file *m,void *v)
include/linux/console.h +5 -3
@@ -15,6 +15,7 @@#define _LINUX_CONSOLE_H_ 1#include <linux/atomic.h> +#include <linux/list.h> #include <linux/types.h> struct vc_data ;
@@ -154,14 +155,16 @@ struct console {u64 seq;unsigned long dropped;void *data; -struct console *next; +struct hlist_node node; }; +extern struct hlist_head console_list; +/* * for_each_console() allows you to iterate on each console */ #define for_each_console (con) \ - for (con = console_drivers; con != NULL; con = con->next) + hlist_for_each_entry(con, &console_list, node)extern int console_set_on_cmdline;extern struct console *early_console;
@@ -174,7 +177,6 @@ enum con_flush_mode {extern int add_preferred_console (char *name,int idx,char *options);extern void register_console (struct console *);extern int unregister_console (struct console *); -extern struct console *console_drivers;extern void console_lock (void );extern int console_trylock (void );extern void console_unlock (void );
kernel/printk/printk.c +55 -46
203 lines not on this page · raw message
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 3/40 printk: Prepare for SRCU console list protection
In reply to John OgnessProvide an NMI-safe SRCU protected variant to walk the console list.
Note that all console fields are now set before adding the console to the list to avoid the console becoming visible by SCRU readers before being fully initialized.
This is a preparatory change for a new console infrastructure which operates independent of the console BKL.
--- .clang-format | 1 + include/linux/console.h | 28 ++++++++++++- kernel/printk/printk.c | 87 ++++++++++++++++++++++++++++++++++------- 3 files changed, 100 insertions(+), 16 deletions(-)
.clang-format +1 -0
@@ -222,6 +222,7 @@ ForEachMacros: - 'for_each_component_dais' - 'for_each_component_dais_safe' - 'for_each_console' + - 'for_each_console_srcu' - 'for_each_cpu' - 'for_each_cpu_and' - 'for_each_cpu_not'
include/linux/console.h +27 -1
@@ -15,7 +15,7 @@#define _LINUX_CONSOLE_H_ 1#include <linux/atomic.h> -#include <linux/list.h> +#include <linux/rculist.h> #include <linux/types.h> struct vc_data ;
@@ -158,8 +158,34 @@ struct console {struct hlist_node node; }; +#ifdef CONFIG_DEBUG_LOCK_ALLOC +extern bool console_srcu_read_lock_is_held (void ); +#else +static inline bool console_srcu_read_lock_is_held (void ) +{ +return 1 ; +} +#endif + +extern int console_srcu_read_lock (void ); +extern void console_srcu_read_unlock (int cookie); +extern struct hlist_head console_list; +/** +* for_each_console_srcu() - Iterator over registered consoles +* @con: struct console pointer used as loop cursor +* +* Although SRCU guarantees the console list will be consistent, the +* struct console fields may be updated by other CPUs while iterating. +* +* Requires console_srcu_read_lock to be held. Can be invoked from +* any context. +*/ +#define for_each_console_srcu (con) \ + hlist_for_each_entry_srcu(con, &console_list, node, \ + console_srcu_read_lock_is_held()) +/* * for_each_console() allows you to iterate on each console */
kernel/printk/printk.c +72 -15
143 lines not on this page · raw message
Signature · 1 line
2.30.2
Re: [PATCH printk v5 03/40] printk: Prepare for SRCU console list protection
Hi John,
Quoted 6 lines · John Ogness
Provide an NMI-safe SRCU protected variant to walk the console list.
Note that all console fields are now set before adding the console to the list to avoid the console becoming visible by SCRU readers before being fully initialized.
Quoted 8 lines
This is a preparatory change for a new console infrastructure which operates independent of the console BKL.
Suggested-by Thomas Gleixner <[email protected]>Signed-off-by John Ogness <[email protected]>Acked-by Miguel Ojeda <[email protected]>Reviewed-by Paul E. McKenney <[email protected]>Reviewed-by Petr Mladek <[email protected]>
I just bisected a boot hang to this change in -next as commit 621a912810a5 ("printk: Prepare for SRCU console list protection"); I have included the bisect log at the end of this message.
The failure occurs while booting ARCH=powerpc pmac32_defconfig in QEMU, during which I see the following message spammed constantly. I have included reproduction steps below, assuming you can use kernel.org's toolchains [1] (I used GCC 11.3.0):
$ make -skj$(nproc) ARCH=powerpc CROSS_COMPILE=powerpc-linux- mrproper pmac32_defconfig
# For proper serial console output
$ scripts/config -e SERIAL_PMACZILOG -e SERIAL_PMACZILOG_CONSOLE
$ make -skj$(nproc) ARCH=powerpc CROSS_COMPILE=powerpc-linux- olddefconfig vmlinux
$ qemu-system-ppc \ -append console=ttyS0 \ -display none \ -initrd rootfs.cpio \ -kernel vmlinux \ -m 128m \ -machine mac99 \ -nodefaults \ -no-reboot \ -serial mon:stdio ... bad: scheduling from the idle thread! CPU: 0 PID: 0 Comm: swapper Not tainted 6.1.0-rc1+ #1 Hardware name: PowerMac3,1 7400 0xc0209 PowerMac Call Trace: [c0bc1db0] [c07f07e0] dump_stack_lvl+0x34/0x50 (unreliable) [c0bc1dd0] [c008429c] dequeue_task_idle+0x34/0x5c [c0bc1df0] [c0820924] __schedule+0x56c/0x5c4 [c0bc1e40] [c08209d0] schedule+0x54/0xfc [c0bc1e60] [c0826034] schedule_timeout+0x13c/0x194 [c0bc1ea0] [c082134c] __wait_for_common+0xcc/0x1f4 [c0bc1ee0] [c00ac8ac] synchronize_srcu+0xc8/0x12c [c0bc1f20] [c00a0230] unregister_console+0xc8/0x10c [c0bc1f40] [c009e314] register_console+0x2f4/0x390 [c0bc1f60] [c0a17510] pmz_console_init+0x34/0x48 [c0bc1f70] [c0a0491c] console_init+0x9c/0xf0 [c0bc1fa0] [c09f5584] start_kernel+0x588/0x6ac [c0bc1ff0] [00003540] 0x3540 ...
The rootfs can be downloaded from [2] at 'images/ppc32/rootfs.cpio.zst' (just decompress it with 'zstd' first) or you can use 'boot-qemu.py' to run QEMU automatically (pass '-h' to see the options available).
If there is any further information I can provide or patches I can test, I am more than happy to do so.
Cheers,
Nathan
[1]: https://mirrors.edge.kernel.org/pub/tools/crosstool/
[2]: https://github.com/ClangBuiltLinux/boot-utils
# bad: [2934ceb4e967b9233d0f97732e47175574a11406] Add linux-next specific files for 20221201
# good: [ef4d3ea40565a781c25847e9cb96c1bd9f462bc6] afs: Fix server->active leak in afs_put_server
git bisect start '2934ceb4e967b9233d0f97732e47175574a11406' 'ef4d3ea40565a781c25847e9cb96c1bd9f462bc6'
# bad: [e21f15c77886e52e4cdb448933ffa9efff48695f] Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
git bisect bad e21f15c77886e52e4cdb448933ffa9efff48695f
# good: [dae6dd6a3a5774175b752856b1a19201317f591d] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
git bisect good dae6dd6a3a5774175b752856b1a19201317f591d
# good: [59b843691d726b332492d70038131d2fb584fc7c] selftests/bpf: Add bench test to arm64 and s390x denylist
git bisect good 59b843691d726b332492d70038131d2fb584fc7c
# bad: [0e4c3a93d8ac956c1697e376ba8f772d342cda6a] Merge branch 'master' of git://linuxtv.org/media_tree.git
git bisect bad 0e4c3a93d8ac956c1697e376ba8f772d342cda6a
# bad: [89e8355104a3b82372fe8ceae026a96097b823b9] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git
git bisect bad 89e8355104a3b82372fe8ceae026a96097b823b9
# bad: [9d9e2018111d42c49c34bc4c59e65163185cb1df] Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
git bisect bad 9d9e2018111d42c49c34bc4c59e65163185cb1df
# bad: [a04b46d8846f8c92bb7697554609d3ae5bc7efb9] Merge branch 'rework/console-list-lock' into for-next
git bisect bad a04b46d8846f8c92bb7697554609d3ae5bc7efb9
# bad: [1a30db5d04673703450f944b3141fd89c70afa70] tty: tty_io: use console_list_lock for list synchronization
git bisect bad 1a30db5d04673703450f944b3141fd89c70afa70
# bad: [feec6b0406f1b71798d31c48d5721b6461e4a636] proc: consoles: document console_lock usage
git bisect bad feec6b0406f1b71798d31c48d5721b6461e4a636
# good: [e29a4915db1480f96e0bc2e928699d086a71f43c] srcu: Debug NMI safety even on archs that don't require it
git bisect good e29a4915db1480f96e0bc2e928699d086a71f43c
# bad: [fd9e5fe0e2a8a8ffc159430eb7ee676978159432] printk: register_console: use "registered" for variable names
git bisect bad fd9e5fe0e2a8a8ffc159430eb7ee676978159432
# good: [c1313d1ab38deb6621045f7d70f0d34f19ec7cfc] serial: kgdboc: Lock console list in probe function
git bisect good c1313d1ab38deb6621045f7d70f0d34f19ec7cfc
# bad: [621a912810a582195eacd96a3536fd057376be21] printk: Prepare for SRCU console list protection
git bisect bad 621a912810a582195eacd96a3536fd057376be21
# good: [7f2dc96716485b01c65f564f2805c558eb0b1a10] printk: Convert console_drivers list to hlist
git bisect good 7f2dc96716485b01c65f564f2805c558eb0b1a1
# first bad commit: [621a912810a582195eacd96a3536fd057376be21] printk: Prepare for SRCU console list protection
John Ogness
maintainerRe: [PATCH printk v5 03/40] printk: Prepare for SRCU console list protection
Hi Nathan,
Thanks for reporting this. Patch below.
@paulmck: Please also take a look below.
Quoted 16 lines · Nathan Chancellor
bad: scheduling from the idle thread!
CPU: 0 PID: 0 Comm: swapper Not tainted 6.1.0-rc1+ #1 Hardware name: PowerMac3,1 7400 0xc0209 PowerMac Call Trace: [c0bc1db0] [c07f07e0] dump_stack_lvl+0x34/0x50 (unreliable) [c0bc1dd0] [c008429c] dequeue_task_idle+0x34/0x5c [c0bc1df0] [c0820924] __schedule+0x56c/0x5c4 [c0bc1e40] [c08209d0] schedule+0x54/0xfc [c0bc1e60] [c0826034] schedule_timeout+0x13c/0x194 [c0bc1ea0] [c082134c] __wait_for_common+0xcc/0x1f4 [c0bc1ee0] [c00ac8ac] synchronize_srcu+0xc8/0x12c [c0bc1f20] [c00a0230] unregister_console+0xc8/0x10c [c0bc1f40] [c009e314] register_console+0x2f4/0x390 [c0bc1f60] [c0a17510] pmz_console_init+0x34/0x48 [c0bc1f70] [c0a0491c] console_init+0x9c/0xf0 [c0bc1fa0] [c09f5584] start_kernel+0x588/0x6ac
Quoted 1 line
[
c0bc1ff0] [00003540]0x3540
This config is using TINY_RCU. Its srcu_synchronize() implementation does not check if it called before scheduling is ready. The following patch will fix it.
@paulmck: Should it check (system_state < SYSTEM_SCHEDULING) instead since TINY_RCU does not use @rcu_scheduler_active?
John Ogness
kernel/rcu/srcutiny.c +3 -0
@@ -197,6 +197,9 @@ void synchronize_srcu(struct srcu_struct *ssp) {struct rcu_synchronize rs; +if (rcu_scheduler_active ==RCU_SCHEDULER_INACTIVE ) +return ; +init_rcu_head_on_stack (&rs.head);init_completion (&rs.completion);call_srcu (ssp, &rs.head, wakeme_after_rcu);
Paul E. McKenney
maintainerRe: [PATCH printk v5 03/40] printk: Prepare for SRCU console list protection
Quoted 25 lines · John Ogness
Hi Nathan,
Thanks for reporting this. Patch below.
@paulmck: Please also take a look below.
Quoted 16 lines · Nathan Chancellor
bad: scheduling from the idle thread!
CPU: 0 PID: 0 Comm: swapper Not tainted 6.1.0-rc1+ #1 Hardware name: PowerMac3,1 7400 0xc0209 PowerMac Call Trace: [c0bc1db0] [c07f07e0] dump_stack_lvl+0x34/0x50 (unreliable) [c0bc1dd0] [c008429c] dequeue_task_idle+0x34/0x5c [c0bc1df0] [c0820924] __schedule+0x56c/0x5c4 [c0bc1e40] [c08209d0] schedule+0x54/0xfc [c0bc1e60] [c0826034] schedule_timeout+0x13c/0x194 [c0bc1ea0] [c082134c] __wait_for_common+0xcc/0x1f4 [c0bc1ee0] [c00ac8ac] synchronize_srcu+0xc8/0x12c [c0bc1f20] [c00a0230] unregister_console+0xc8/0x10c [c0bc1f40] [c009e314] register_console+0x2f4/0x390 [c0bc1f60] [c0a17510] pmz_console_init+0x34/0x48 [c0bc1f70] [c0a0491c] console_init+0x9c/0xf0 [c0bc1fa0] [c09f5584] start_kernel+0x588/0x6acQuoted 1 line
[
c0bc1ff0] [00003540]0x3540
Quoted 6 lines
This config is using
TINY_RCU. Itssrcu_synchronize()implementation does not check if it called before scheduling is ready. The following patch will fix it.@paulmck: Should it check (
system_state<SYSTEM_SCHEDULING) instead sinceTINY_RCUdoes not use @rcu_scheduler_active?
Thank you for chasing this down, John!
You are exactly right, and I therefore need to pull this into the pile for the upcoming merge window:
dbc6ca150842 ("srcu: Make Tiny synchronize_srcu() check for readers")
And kudos to Zqiang for a proactive fix! ;-)
I will add your (John's) Tested-by, but please let me know if this is inappropriate.
Thanx, Paul
Quoted 16 lines
John Ogness
kernel/rcu/srcutiny.c +3
-0@@ -197,6 +197,9 @@ void synchronize_srcu(struct srcu_struct *ssp) {struct rcu_synchronize rs; +if (rcu_scheduler_active ==RCU_SCHEDULER_INACTIVE ) +return ; +init_rcu_head_on_stack (&rs.head);init_completion (&rs.completion);call_srcu (ssp, &rs.head, wakeme_after_rcu);
Re: [PATCH printk v5 03/40] printk: Prepare for SRCU console list protection
Quoted 6 lines · Paul E. McKenney
I therefore need to pull this into the pile for the upcoming merge window:
dbc6ca150842("srcu: Make Tinysynchronize_srcu()check for readers")And kudos to Zqiang for a proactive fix! ;-)
Yes! Great job!
Quoted 2 lines
I will add your (John's) Tested-by, but please let me know if this is inappropriate.
Sure.
John
Re: [PATCH printk v5 03/40] printk: Prepare for SRCU console list protection
Quoted 8 lines · John Ogness
Quoted 6 lines · Paul E. McKenney
I therefore need to pull this into the pile for the upcoming merge window:
dbc6ca150842("srcu: Make Tinysynchronize_srcu()check for readers")And kudos to Zqiang for a proactive fix! ;-)
Quoted 8 lines
Yes! Great job!
Quoted 2 lines
I will add your (John's) Tested-by, but please let me know if this is inappropriate.
Sure.
Tested-by John Ogness <[email protected]>
Applied, thank you!
The new -rcu branch is srcunmisafe.2022.12.01a.
Adding Stephen Rothwell on CC because Mr. Murphy says that this change will once again mess up -next. Apologies in advance!!!
Thanx, Paul
Petr Mladek
maintainerRe: [PATCH printk v5 03/40] printk: Prepare for SRCU console list protection
Quoted 16 lines · Paul E. McKenney
Quoted 15 lines · John Ogness
Quoted 6 lines · Paul E. McKenney
I therefore need to pull this into the pile for the upcoming merge window:
dbc6ca150842("srcu: Make Tinysynchronize_srcu()check for readers")And kudos to Zqiang for a proactive fix! ;-)
Yes! Great job!
Quoted 2 lines
I will add your (John's) Tested-by, but please let me know if this is inappropriate.
Sure.
Quoted 8 lines
Quoted 1 line
Tested-by John Ogness <[email protected]>Applied, thank you!
The new -rcu branch is srcunmisafe.2022.12.01a.
Adding Stephen Rothwell on CC because Mr. Murphy says that this change will once again mess up -next. Apologies in advance!!!
I have rebased printk/linux.git, branch rework/console-list-lock on top of srcunmisafe.2022.12.01a, commit 51f5f78a4f804aeb73cf ("srcu:
Make Tiny synchronize_srcu() check for readers").
I hope that it will be OK.
Thanks a lot for nailing this down. It looked like a mystery to me.
Best Regards,
Petr
John Ogness
maintainerPATCH v5 4/40 printk: register_console: use "registered" for variable names
In reply to John OgnessThe @bootcon_enabled and @realcon_enabled local variables actually represent if such console types are registered. In general there has been a confusion about enabled vs. registered. Incorrectly naming such variables promotes such confusion.
Rename the variables to _registered.
--- kernel/printk/printk.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
kernel/printk/printk.c +7 -7
@@ -3156,8 +3156,8 @@ static void try_enable_default_console(struct console *newcon)void register_console (struct console *newcon) {struct console *con; -bool bootcon_enabled = false; -bool realcon_enabled = false; +bool bootcon_registered = false; +bool realcon_registered = false;int err;for_each_console (con) {
@@ -3168,13 +3168,13 @@ void register_console(struct console *newcon)for_each_console (con) {if (con->flags &CON_BOOT ) - bootcon_enabled = true; + bootcon_registered = true;else - realcon_enabled = true; + realcon_registered = true; }/* Do not register boot consoles when there already is a real one. */ -if (newcon->flags &CON_BOOT && realcon_enabled) { +if ((newcon->flags &CON_BOOT ) && realcon_registered) {pr_info ("Too late to register bootconsole %s%d\n" , newcon->name, newcon->index);return ;
@@ -3216,7 +3216,7 @@ void register_console(struct console *newcon)* the real console are the same physical device, it's annoying to * see the beginning boot messages twice */ -if (bootcon_enabled && +if (bootcon_registered && ((newcon->flags & (CON_CONSDEV |CON_BOOT )) ==CON_CONSDEV )) { newcon->flags &= ~CON_PRINTBUFFER ; }
@@ -3268,7 +3268,7 @@ void register_console(struct console *newcon)* went to the bootconsole (that they do not see on the real console) */ con_printk (KERN_INFO , newcon,"enabled\n" ); -if (bootcon_enabled && +if (bootcon_registered && ((newcon->flags & (CON_CONSDEV |CON_BOOT )) ==CON_CONSDEV ) && !keep_bootcon) {struct hlist_node *tmp;
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 5/40 printk: move @seq initialization to helper
In reply to John OgnessThe code to initialize @seq for a new console needs to consider more factors when choosing an initial value. Move the code into a helper function console_init_seq() "as is" so this code can be expanded without causing register_console() to become too long. A later commit will implement the additional code.
--- kernel/printk/printk.c | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-)
kernel/printk/printk.c +14 -9
@@ -3131,6 +3131,19 @@ static void try_enable_default_console(struct console *newcon) (con->flags & CON_BOOT) ? "boot" : "", \ con->name, con->index, ##__VA_ARGS__) +static void console_init_seq (struct console *newcon) +{ +if (newcon->flags &CON_PRINTBUFFER ) { +/* Get a consistent copy of @syslog_seq. */ +mutex_lock (&syslog_lock); + newcon->seq = syslog_seq; +mutex_unlock (&syslog_lock); + }else { +/* Begin with next message. */ + newcon->seq =prb_next_seq (prb); + } +} +#define console_first () \ hlist_entry(console_list.first, struct console, node)
@@ -3222,15 +3235,7 @@ void register_console(struct console *newcon) } newcon->dropped =0 ; -if (newcon->flags &CON_PRINTBUFFER ) { -/* Get a consistent copy of @syslog_seq. */ -mutex_lock (&syslog_lock); - newcon->seq = syslog_seq; -mutex_unlock (&syslog_lock); - }else { -/* Begin with next message. */ - newcon->seq =prb_next_seq (prb); - } +console_init_seq (newcon);/* * Put this console in the list - keep the
Signature · 1 line
2.30.2
Re: [PATCH printk v5 05/40] printk: move @seq initialization to helper
Quoted 7 lines · John Ogness
The code to initialize @seq for a new console needs to consider more factors when choosing an initial value. Move the code into a helper function
console_init_seq()"as is" so this code can be expanded without causingregister_console()to become too long. A later commit will implement the additional code.Signed-off-by John Ogness <[email protected]>
Best Regards,
Petr
John Ogness
maintainerPATCH v5 6/40 printk: fix setting first seq for consoles
In reply to John OgnessIt used to be that all consoles were synchronized with respect to which message they were printing. After commit a699449bb13b ("printk:
refactor and rework printing logic"), all consoles have their own @seq for tracking which message they are on. That commit also changed how the initial sequence number was chosen. Instead of choosing the next non-printed message, it chose the sequence number of the next message that will be added to the ringbuffer.
That change created a possibility that a non-boot console taking over for a boot console might skip messages if the boot console was behind and did not have a chance to catch up before being unregistered.
Since it is not known which boot console is the same device, flush all consoles and, if necessary, start with the message of the enabled boot console that is the furthest behind. If no boot consoles are enabled, begin with the next message that will be added to the ringbuffer.
Also, since boot consoles are meant to be used at boot time, handle them the same as CON_PRINTBUFFER to ensure that no initial messages are skipped.
--- kernel/printk/printk.c | 50 +++++++++++++++++++++++++++++++++++++----- 1 file changed, 45 insertions(+), 5 deletions(-)
kernel/printk/printk.c +45 -5
@@ -3131,16 +3131,56 @@ static void try_enable_default_console(struct console *newcon) (con->flags & CON_BOOT) ? "boot" : "", \ con->name, con->index, ##__VA_ARGS__) -static void console_init_seq (struct console *newcon) +static void console_init_seq (struct console *newcon,bool bootcon_registered) { -if (newcon->flags &CON_PRINTBUFFER ) { +struct console *con; +bool handover; + +if (newcon->flags & (CON_PRINTBUFFER |CON_BOOT )) {/* Get a consistent copy of @syslog_seq. */ mutex_lock (&syslog_lock); newcon->seq = syslog_seq;mutex_unlock (&syslog_lock); }else { -/* Begin with next message. */ +/* Begin with next message added to ringbuffer. */ newcon->seq =prb_next_seq (prb); + +/* +* If any enabled boot consoles are due to be unregistered +* shortly, some may not be caught up and may be the same +* device as @newcon. Since it is not known which boot console +* is the same device, flush all consoles and, if necessary, +* start with the message of the enabled boot console that is +* the furthest behind. +*/ +if (bootcon_registered && !keep_bootcon) { +/* +* Flush all consoles and set the console to start at +* the next unprinted sequence number. +*/ +if (!console_flush_all (true, &newcon->seq, &handover)) { +/* +* Flushing failed. Just choose the lowest +* sequence of the enabled boot consoles. +*/ + +/* +* If there was a handover, this context no +* longer holds the console_lock. +*/ +if (handover) +console_lock (); + + newcon->seq =prb_next_seq (prb); +for_each_console (con) { +if ((con->flags &CON_BOOT ) && + (con->flags &CON_ENABLED ) && + con->seq < newcon->seq) { + newcon->seq = con->seq; + } + } + } + } } }
@@ -3235,13 +3275,13 @@ void register_console(struct console *newcon) } newcon->dropped =0 ; -console_init_seq (newcon); +console_lock (); +console_init_seq (newcon, bootcon_registered);/* * Put this console in the list - keep the * preferred driver at the head of the list. */ -console_lock ();if (hlist_empty (&console_list)) {/* Ensure CON_CONSDEV is always set for the head. */ newcon->flags |=CON_CONSDEV ;
Signature · 1 line
2.30.2
Re: [PATCH printk v5 06/40] printk: fix setting first seq for consoles
Quoted 18 lines · John Ogness
It used to be that all consoles were synchronized with respect to which message they were printing. After commit
a699449bb13b("printk:
refactor and rework printing logic"), all consoles have their own @seq for tracking which message they are on. That commit also changed how the initial sequence number was chosen. Instead of choosing the next non-printed message, it chose the sequence number of the next message that will be added to the ringbuffer.That change created a possibility that a non-boot console taking over for a boot console might skip messages if the boot console was behind and did not have a chance to catch up before being unregistered.
Since it is not known which boot console is the same device, flush all consoles and, if necessary, start with the message of the enabled boot console that is the furthest behind. If no boot consoles are enabled, begin with the next message that will be added to the ringbuffer.
Quoted 5 lines
Also, since boot consoles are meant to be used at boot time, handle them the same as
CON_PRINTBUFFERto ensure that no initial messages are skipped.Signed-off-by John Ogness <[email protected]>
See one possible improvement below.
Quoted 38 lines
kernel/printk/printk.c +22
-3@@ -3131,16 +3131,56 @@ static void try_enable_default_console(struct console *newcon) (con->flags & CON_BOOT) ? "boot" : "", \ con->name, con->index, ##__VA_ARGS__) -static void console_init_seq (struct console *newcon) +static void console_init_seq (struct console *newcon,bool bootcon_registered) { -if (newcon->flags &CON_PRINTBUFFER ) { +struct console *con; +bool handover; + +if (newcon->flags & (CON_PRINTBUFFER |CON_BOOT )) {/* Get a consistent copy of @syslog_seq. */ mutex_lock (&syslog_lock); newcon->seq = syslog_seq;mutex_unlock (&syslog_lock); }else { -/* Begin with next message. */ +/* Begin with next message added to ringbuffer. */ newcon->seq =prb_next_seq (prb); + +/* +* If any enabled boot consoles are due to be unregistered +* shortly, some may not be caught up and may be the same +* device as @newcon. Since it is not known which boot console +* is the same device, flush all consoles and, if necessary, +* start with the message of the enabled boot console that is +* the furthest behind. +*/ +if (bootcon_registered && !keep_bootcon) { +/* +* Flush all consoles and set the console to start at +* the next unprinted sequence number. +*/ +if (!console_flush_all (true, &newcon->seq, &handover)) { +/*
kernel/printk/printk.c static void try_enable_default_console(struct console *newcon) · line 3172
Quoted 10 lines
kernel/printk/printk.c +10
-0+* Flushing failed. Just choose the lowest +* sequence of the enabled boot consoles. +*/ + +/* +* If there was a handover, this context no +* longer holds the console_lock. +*/ +if (handover) +console_lock ();
Another improvement might be to disable handover in this case. It would be safe because we are in a sleepable context. It would increase the chance that console_fluhs_all() succeeded.
On the other hand, it might cause that this caller gets stuck here because of flood of messages printed by another caller.
We could do this later when there are problems with this approach. The problem with the handover has been there even before.
I do not want to delay this patchset by discussion this non-critical problem to the death ;-)
Best Regards,
Petr
John Ogness
maintainerRe: [PATCH printk v5 06/40] printk: fix setting first seq for consoles
Quoted 3 lines · Petr Mladek
Another improvement might be to disable handover in this case. It would be safe because we are in a sleepable context. It would increase the chance that
console_flush_all()succeeded.
I also considered this. The problem is that you cannot disable the handover with the current API and it seemed crazy to dig all the up just for this.
Quoted 2 lines
We could do this later when there are problems with this approach. The problem with the handover has been there even before.
Agreed.
Quoted 2 lines
I do not want to delay this patchset by discussion this non-critical problem to the death ;-)
Thanks! :-)
John
John Ogness
maintainerPATCH v5 7/40 um: kmsg_dump: only dump when no output console available
In reply to John OgnessThe initial intention of the UML kmsg_dumper is to dump the kernel buffers to stdout if there is no console available to perform the regular crash output.
However, if ttynull was registered as a console, no crash output was seen. Commit e23fe90dec28 ("um: kmsg_dumper: always dump when not tty console") tried to fix this by performing the kmsg_dump unless the stdio console was behind /dev/console or enabled. But this allowed kmsg dumping to occur even if other non-stdio consoles will output the crash output. Also, a console being the driver behind /dev/console has nothing to do with a crash scenario.
Restore the initial intention by dumping the kernel buffers to stdout only if a non-ttynull console is registered and enabled. Also add detailed comments so that it is clear why these rules are applied.
--- arch/um/kernel/kmsg_dump.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
arch/um/kernel/kmsg_dump.c +12 -3
@@ -17,13 +17,22 @@ static void kmsg_dumper_stdout(struct kmsg_dumper *dumper,unsigned long flags;size_t len =0 ; -/* only dump kmsg when no console is available */ +/* +* If no consoles are available to output crash information, dump +* the kmsg buffer to stdout. +*/ +if (!console_trylock ())return ;for_each_console (con) { -if (strcmp (con->name,"tty" ) ==0 && - (con->flags & (CON_ENABLED |CON_CONSDEV )) !=0 ) { +/* +* The ttynull console and disabled consoles are ignored +* since they cannot output. All other consoles are +* expected to output the crash information. +*/ +if (strcmp (con->name,"ttynull" ) !=0 && + (con->flags &CON_ENABLED )) {break ; } }
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 8/40 tty: serial: kgdboc: document console_lock usage
In reply to John Ognesskgdboc_earlycon_init() uses the console_lock to ensure that no consoles are unregistered until the kgdboc_earlycon is setup. This is necessary because the trapping of the exit() callback assumes that the exit() callback is not called before the trap is setup.
Explicitly document this non-typical console_lock usage.
--- drivers/tty/serial/kgdboc.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/tty/serial/kgdboc.c +8 -0
@@ -530,6 +530,14 @@ static int __init kgdboc_earlycon_init(char *opt)* Look for a matching console, or if the name was left blank just * pick the first one we find. */ + +/* +* Hold the console_lock to guarantee that no consoles are +* unregistered until the kgdboc_earlycon setup is complete. +* Trapping the exit() callback relies on exit() not being +* called until the trap is setup. This also allows safe +* traversal of the console list and race-free reading of @flags. +*/ console_lock ();for_each_console (con) { if (con->write && con->read &&
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 9/40 tty: tty_io: document console_lock usage
In reply to John Ognessshow_cons_active() uses the console_lock to gather information on registered consoles. Since the console_lock is being used for multiple reasons, explicitly document these reasons. This will be useful when the console_lock is split into fine-grained locking.
--- drivers/tty/tty_io.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
drivers/tty/tty_io.c +10 -0
@@ -3526,6 +3526,16 @@ static ssize_t show_cons_active(struct device *dev,struct console *c;ssize_t count =0 ; +/* +* Hold the console_lock to guarantee that no consoles are +* unregistered until all console processing is complete. +* This also allows safe traversal of the console list and +* race-free reading of @flags. +* +* Take console_lock to serialize device() callback with +* other console operations. For example, fg_console is +* modified under console_lock when switching vt. +*/ console_lock ();for_each_console (c) {if (!c->device)
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 10/40 proc: consoles: document console_lock usage
In reply to John OgnessThe console_lock is held throughout the start/show/stop procedure to print out device/driver information about all registered consoles. Since the console_lock is being used for multiple reasons, explicitly document these reasons. This will be useful when the console_lock is split into fine-grained locking.
--- fs/proc/consoles.c | 9 +++++++++ 1 file changed, 9 insertions(+)
fs/proc/consoles.c +9 -0
@@ -63,6 +63,15 @@ static void *c_start(struct seq_file *m, loff_t *pos)struct console *con;loff_t off =0 ; +/* +* Take console_lock to serialize device() callback with +* other console operations. For example, fg_console is +* modified under console_lock when switching vt. +* +* Hold the console_lock to guarantee safe traversal of the +* console list. SRCU cannot be used because there is no +* place to store the SRCU cookie. +*/ console_lock ();for_each_console (con)if (off++ == *pos)
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 11/40 printk: introduce console_list_lock
In reply to John OgnessCurrently there exist races in register_console(), where the types of registered consoles are checked (without holding the console_lock) and then after acquiring the console_lock, it is assumed that the list has not changed. Also, some code that performs console_unregister() make similar assumptions.
It might be possible to fix these races using the console_lock. But it would require a complex analysis of all console drivers to make sure that the console_lock is not taken in match() and setup() callbacks. And we really prefer to split up and reduce the responsibilities of console_lock rather than expand its complexity. Therefore, introduce a new console_list_lock to provide full synchronization for any console list changes.
In addition, also use console_list_lock for synchronization of console->flags updates. All flags are either static or modified only during the console registration. There are only two exceptions.
The first exception is CON_ENABLED, which is also modified by console_start()/console_stop(). Therefore, these functions must also take the console_list_lock.
The second exception is when the flags are modified by the console driver init code before the console is registered. These will be ignored because they are not visible to the rest of the system via the console_drivers list.
Note that one of the various responsibilities of the console_lock is also intended to provide console list and console->flags synchronization. Later changes will update call sites relying on the console_lock for these purposes. Once all call sites have been updated, the console_lock will be relieved of synchronizing console_list and console->flags updates.
--- include/linux/console.h | 23 +++++++++-- kernel/printk/printk.c | 88 ++++++++++++++++++++++++++++++++++++----- 2 files changed, 99 insertions(+), 12 deletions(-)
include/linux/console.h +20 -3
@@ -158,6 +158,14 @@ struct console {struct hlist_node node; }; +#ifdef CONFIG_LOCKDEP +extern void lockdep_assert_console_list_lock_held (void ); +#else +static inline void lockdep_assert_console_list_lock_held (void ) +{ +} +#endif +#ifdef CONFIG_DEBUG_LOCK_ALLOC extern bool console_srcu_read_lock_is_held (void );#else
@@ -170,6 +178,9 @@ static inline bool console_srcu_read_lock_is_held(void)extern int console_srcu_read_lock (void );extern void console_srcu_read_unlock (int cookie); +extern void console_list_lock(void) __acquires(console_mutex); +extern void console_list_unlock(void) __releases(console_mutex); +extern struct hlist_head console_list;/**
@@ -186,10 +197,16 @@ extern struct hlist_head console_list;hlist_for_each_entry_srcu (con, &console_list, node, \console_srcu_read_lock_is_held ()) -/* -* for_each_console() allows you to iterate on each console +/** +* for_each_console() - Iterator over registered consoles +* @con: struct console pointer used as loop cursor +* +* The console list and the console->flags are immutable while iterating. +* +* Requires console_list_lock to be held. */ -#define for_each_console (con) \ +#define for_each_console (con) \ + lockdep_assert_console_list_lock_held(); \ hlist_for_each_entry(con, &console_list, node)extern int console_set_on_cmdline;
kernel/printk/printk.c +79 -9
185 lines not on this page · raw message
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v6 11/40 printk: introduce console_list_lock
Currently there exist races in register_console(), where the types of registered consoles are checked (without holding the console_lock) and then after acquiring the console_lock, it is assumed that the list has not changed. Also, some code that performs console_unregister() make similar assumptions.
It might be possible to fix these races using the console_lock. But it would require a complex analysis of all console drivers to make sure that the console_lock is not taken in match() and setup() callbacks. And we really prefer to split up and reduce the responsibilities of console_lock rather than expand its complexity. Therefore, introduce a new console_list_lock to provide full synchronization for any console list changes.
In addition, also use console_list_lock for synchronization of console->flags updates. All flags are either static or modified only during the console registration. There are only two exceptions.
The first exception is CON_ENABLED, which is also modified by console_start()/console_stop(). Therefore, these functions must also take the console_list_lock.
The second exception is when the flags are modified by the console driver init code before the console is registered. These will be ignored because they are not visible to the rest of the system via the console_drivers list.
Note that one of the various responsibilities of the console_lock is also intended to provide console list and console->flags synchronization. Later changes will update call sites relying on the console_lock for these purposes. Once all call sites have been updated, the console_lock will be relieved of synchronizing console_list and console->flags updates.
---
Stephen reported [0] a build failure with linux-next. The problem was a missing EXPORT of @lockdep_assert_console_list_lock_held for when drivers are built as modules.
[0] https://lore.kernel.org/lkml/[email protected]
include/linux/console.h | 23 +++++++++-- kernel/printk/printk.c | 89 ++++++++++++++++++++++++++++++++++++----- 2 files changed, 100 insertions(+), 12 deletions(-)
include/linux/console.h +20 -3
@@ -158,6 +158,14 @@ struct console {struct hlist_node node; }; +#ifdef CONFIG_LOCKDEP +extern void lockdep_assert_console_list_lock_held (void ); +#else +static inline void lockdep_assert_console_list_lock_held (void ) +{ +} +#endif +#ifdef CONFIG_DEBUG_LOCK_ALLOC extern bool console_srcu_read_lock_is_held (void );#else
@@ -170,6 +178,9 @@ static inline bool console_srcu_read_lock_is_held(void)extern int console_srcu_read_lock (void );extern void console_srcu_read_unlock (int cookie); +extern void console_list_lock(void) __acquires(console_mutex); +extern void console_list_unlock(void) __releases(console_mutex); +extern struct hlist_head console_list;/**
@@ -186,10 +197,16 @@ extern struct hlist_head console_list;hlist_for_each_entry_srcu (con, &console_list, node, \console_srcu_read_lock_is_held ()) -/* -* for_each_console() allows you to iterate on each console +/** +* for_each_console() - Iterator over registered consoles +* @con: struct console pointer used as loop cursor +* +* The console list and the console->flags are immutable while iterating. +* +* Requires console_list_lock to be held. */ -#define for_each_console (con) \ +#define for_each_console (con) \ + lockdep_assert_console_list_lock_held(); \ hlist_for_each_entry(con, &console_list, node)extern int console_set_on_cmdline;
kernel/printk/printk.c +80 -9
186 lines not on this page · raw message
Signature · 1 line
2.30.2
Petr Mladek
maintainerRe: [PATCH printk v6 11/40] printk: introduce console_list_lock
Quoted 37 lines · John Ogness
Currently there exist races in
register_console(), where the types of registered consoles are checked (without holding theconsole_lock) and then after acquiring theconsole_lock, it is assumed that the list has not changed. Also, some code that performsconsole_unregister()make similar assumptions.It might be possible to fix these races using the
console_lock. But it would require a complex analysis of all console drivers to make sure that theconsole_lockis not taken inmatch()andsetup()callbacks. And we really prefer to split up and reduce the responsibilities ofconsole_lockrather than expand its complexity. Therefore, introduce a newconsole_list_lockto provide full synchronization for any console list changes.In addition, also use
console_list_lockfor synchronization ofconsole->flagsupdates. All flags are either static or modified only during the console registration. There are only two exceptions.The first exception is
CON_ENABLED, which is also modified by console_start()/console_stop(). Therefore, these functions must also take theconsole_list_lock.The second exception is when the flags are modified by the console driver init code before the console is registered. These will be ignored because they are not visible to the rest of the system via the
console_driverslist.Note that one of the various responsibilities of the
console_lockis also intended to provide console list andconsole->flagssynchronization. Later changes will update call sites relying on theconsole_lockfor these purposes. Once all call sites have been updated, theconsole_lockwill be relieved of synchronizingconsole_listandconsole->flagsupdates.Suggested-by Thomas Gleixner <[email protected]>Signed-off-by John Ogness <[email protected]>Reviewed-by Petr Mladek <[email protected]>
Quoted 6 lines
---
Stephen reported [0] a build failure with linux-next. The problem was a missing EXPORT of @lockdep_assert_console_list_lock_held for when drivers are built as modules.
JFYI, the branch rework/console-list-lock in printk/linux.git has been rebased using this version of the patch.
Thanks a lot for the fix.
Best Regards,
Petr
John Ogness
maintainerPATCH v5 12/40 console: introduce wrappers to read/write console flags
In reply to John OgnessAfter switching to SRCU for console list iteration, some readers will begin readings console->flags as a data race. Locklessly reading console->flags provides a consistent value because there is at most one CPU modifying console->flags and that CPU is using only read-modify-write operations.
Introduce a wrapper for SRCU iterators to read console flags. Introduce a matching wrapper to write to flags of registered consoles. Writing to flags of registered consoles is synchronized by the console_list_lock.
--- include/linux/console.h | 45 +++++++++++++++++++++++++++++++++++++++++ kernel/printk/printk.c | 10 ++++----- 2 files changed, 50 insertions(+), 5 deletions(-)
include/linux/console.h +45 -0
@@ -183,6 +183,51 @@ extern void console_list_unlock(void) __releases(console_mutex);extern struct hlist_head console_list; +/** +* console_srcu_read_flags - Locklessly read the console flags +* @con: struct console pointer of console to read flags from +* +* This function provides the necessary READ_ONCE() and data_race() +* notation for locklessly reading the console flags. The READ_ONCE() +* in this function matches the WRITE_ONCE() when @flags are modified +* for registered consoles with console_srcu_write_flags(). +* +* Only use this function to read console flags when locklessly +* iterating the console list via srcu. +* +* Context: Any context. +*/ +static inline short console_srcu_read_flags (const struct console *con) +{ +WARN_ON_ONCE (!console_srcu_read_lock_is_held ()); + +/* +* Locklessly reading console->flags provides a consistent +* read value because there is at most one CPU modifying +* console->flags and that CPU is using only read-modify-write +* operations to do so. +*/ +return data_race (READ_ONCE (con->flags)); +} + +/** +* console_srcu_write_flags - Write flags for a registered console +* @con: struct console pointer of console to write flags to +* @flags: new flags value to write +* +* Only use this function to write flags for registered consoles. It +* requires holding the console_list_lock. +* +* Context: Any context. +*/ +static inline void console_srcu_write_flags (struct console *con,short flags) +{ +lockdep_assert_console_list_lock_held (); + +/* This matches the READ_ONCE() in console_srcu_read_flags(). */ +WRITE_ONCE (con->flags, flags); +} +/** * for_each_console_srcu() - Iterator over registered consoles * @con: struct console pointer used as loop cursor
kernel/printk/printk.c +5 -5
@@ -3068,7 +3068,7 @@ void console_stop(struct console *console)__pr_flush (console,1000 , true);console_list_lock ();console_lock (); - console->flags &= ~CON_ENABLED ; +console_srcu_write_flags (console, console->flags & ~CON_ENABLED );console_unlock ();console_list_unlock ();
@@ -3086,7 +3086,7 @@ void console_start(struct console *console) {console_list_lock ();console_lock (); - console->flags |=CON_ENABLED ; +console_srcu_write_flags (console, console->flags |CON_ENABLED );console_unlock ();console_list_unlock ();__pr_flush (console,1000 , true);
@@ -3342,7 +3342,7 @@ void register_console(struct console *newcon) }else if (newcon->flags &CON_CONSDEV ) {/* Only the new head can have CON_CONSDEV set. */ -console_first ()->flags &= ~CON_CONSDEV ; +console_srcu_write_flags (console_first (),console_first ()->flags & ~CON_CONSDEV );hlist_add_head_rcu (&newcon->node, &console_list); }else {
@@ -3399,7 +3399,7 @@ static int unregister_console_locked(struct console *console)console_lock ();/* Disable it unconditionally */ - console->flags &= ~CON_ENABLED ; +console_srcu_write_flags (console, console->flags & ~CON_ENABLED );if (hlist_unhashed (&console->node)) {console_unlock ();
@@ -3418,7 +3418,7 @@ static int unregister_console_locked(struct console *console)* console has any device attached. Oh well.... */ if (!hlist_empty (&console_list) && console->flags &CON_CONSDEV ) -console_first ()->flags |=CON_CONSDEV ; +console_srcu_write_flags (console_first (),console_first ()->flags |CON_CONSDEV );console_unlock ();
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 13/40 um: kmsg_dumper: use srcu console list iterator
In reply to John OgnessRather than using the console_lock to guarantee safe console list traversal, use srcu console list iteration.
--- arch/um/kernel/kmsg_dump.c | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-)
arch/um/kernel/kmsg_dump.c +5 -8
@@ -16,29 +16,26 @@ static void kmsg_dumper_stdout(struct kmsg_dumper *dumper,struct console *con;unsigned long flags;size_t len =0 ; +int cookie;/* * If no consoles are available to output crash information, dump * the kmsg buffer to stdout. */ -if (!console_trylock ()) -return ; - -for_each_console (con) { + cookie =console_srcu_read_lock (); +for_each_console_srcu (con) {/* * The ttynull console and disabled consoles are ignored * since they cannot output. All other consoles are * expected to output the crash information. */ if (strcmp (con->name,"ttynull" ) !=0 && - (con->flags &CON_ENABLED )) { + (console_srcu_read_flags (con) &CON_ENABLED )) {break ; } } - -console_unlock (); - +console_srcu_read_unlock (cookie);if (con)return ;
Signature · 7 lines
2.30.2 _______________________________________________ linux-um mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-um
John Ogness
maintainerPATCH v5 14/40 kdb: use srcu console list iterator
In reply to John OgnessGuarantee safe iteration of the console list by using SRCU.
--- kernel/debug/kdb/kdb_io.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)
kernel/debug/kdb/kdb_io.c +16 -2
@@ -545,6 +545,7 @@ static void kdb_msg_write(const char *msg, int msg_len) {struct console *c;const char *cp; +int cookie;int len;if (msg_len ==0 )
@@ -558,8 +559,20 @@ static void kdb_msg_write(const char *msg, int msg_len) cp++; } -for_each_console (c) { -if (!(c->flags &CON_ENABLED )) +/* +* The console_srcu_read_lock() only provides safe console list +* traversal. The use of the ->write() callback relies on all other +* CPUs being stopped at the moment and console drivers being able to +* handle reentrance when @oops_in_progress is set. +* +* There is no guarantee that every console driver can handle +* reentrance in this way; the developer deploying the debugger +* is responsible for ensuring that the console drivers they +* have selected handle reentrance appropriately. +*/ + cookie =console_srcu_read_lock (); +for_each_console_srcu (c) { +if (!(console_srcu_read_flags (c) &CON_ENABLED ))continue ;if (c == dbg_io_ops->cons)continue ;
@@ -577,6 +590,7 @@ static void kdb_msg_write(const char *msg, int msg_len) --oops_in_progress;touch_nmi_watchdog (); } +console_srcu_read_unlock (cookie); }int vkdb_printf (enum kdb_msgsrc src,const char *fmt,va_list ap)
Signature · 1 line
2.30.2
Re: [PATCH printk v5 14/40] kdb: use srcu console list iterator
Hi,
Quoted 9 lines · John Ogness
Guarantee safe iteration of the console list by using SRCU.
Signed-off-by John Ogness <[email protected]>Reviewed-by Petr Mladek <[email protected]>Reviewed-by Aaron Tomlin <[email protected]>--- kernel/debug/kdb/kdb_io.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)
Without becoming an expert on this whole series, this seems reasonable to me.
John Ogness
maintainerPATCH v5 15/40 printk: console_flush_all: use srcu console list iterator
In reply to John OgnessGuarantee safe iteration of the console list by using SRCU.
Note that in the case of a handover, the SRCU read lock is also released. This is documented in the function description and as comments in the code. It is a bit tricky, but this preserves the lockdep lock ordering for the context handing over the console_lock:
console_lock()
| mutex_acquire(&console_lock_dep_map) <-- console lock
|
console_unlock()
| console_flush_all() | | srcu_read_lock(&console_srcu) <-- srcu lock | | console_emit_next_record() | | | console_lock_spinning_disable_and_check() | | | | srcu_read_unlock(&console_srcu) <-- srcu unlock | | | | mutex_release(&console_lock_dep_map) <-- console unlock
--- kernel/printk/printk.c | 50 +++++++++++++++++++++++++++++------------- 1 file changed, 35 insertions(+), 15 deletions(-)
kernel/printk/printk.c +35 -15
@@ -1893,13 +1893,13 @@ static void console_lock_spinning_enable(void)* safe to start busy waiting for the lock. Second, it checks if * there is a busy waiter and passes the lock rights to her. * -* Important: Callers lose the lock if there was a busy waiter. -* They must not touch items synchronized by console_lock -* in this case. +* Important: Callers lose both the console_lock and the SRCU read lock if +* there was a busy waiter. They must not touch items synchronized by +* console_lock or SRCU read lock in this case. * * Return: 1 if the lock rights were passed, 0 otherwise. */ -static int console_lock_spinning_disable_and_check (void ) +static int console_lock_spinning_disable_and_check (int cookie) {int waiter;
@@ -1918,6 +1918,12 @@ static int console_lock_spinning_disable_and_check(void)spin_release (&console_owner_dep_map, _THIS_IP_); +/* +* Preserve lockdep lock ordering. Release the SRCU read lock before +* releasing the console_lock. +*/ +console_srcu_read_unlock (cookie); +/* * Hand off console_lock to waiter. The waiter will perform * the up(). After this, the waiter is the console_lock owner.
@@ -2401,7 +2407,7 @@ static ssize_t msg_print_ext_body(char *buf, size_t size, char *text, size_t text_len, struct dev_printk_info *dev_info) { return 0; }static void console_lock_spinning_enable (void ) { } -static int console_lock_spinning_disable_and_check (void ) {return 0 ; } +static int console_lock_spinning_disable_and_check (int cookie) {return 0 ; }static void call_console_driver (struct console *con,const char *text,size_t len,char *dropped_text) {
@@ -2743,16 +2749,18 @@ static void __console_unlock(void)* DROPPED_TEXT_MAX. Otherwise @dropped_text must be NULL. * * @handover will be set to true if a printk waiter has taken over the -* console_lock, in which case the caller is no longer holding the -* console_lock. Otherwise it is set to false. +* console_lock, in which case the caller is no longer holding both the +* console_lock and the SRCU read lock. Otherwise it is set to false. +* +* @cookie is the cookie from the SRCU read lock. * * Returns false if the given console has no next record to print, otherwise * true. * -* Requires the console_lock. +* Requires the console_lock and the SRCU read lock. */ static bool console_emit_next_record (struct console *con,char *text,char *ext_text, -char *dropped_text,bool *handover) +char *dropped_text,bool *handover,int cookie) {static int panic_console_dropped;struct printk_info info;
@@ -2812,7 +2820,7 @@ static bool console_emit_next_record(struct console *con, char *text, char *ext_ con->seq++; - *handover =console_lock_spinning_disable_and_check (); + *handover =console_lock_spinning_disable_and_check (cookie);printk_safe_exit_irqrestore (flags); skip:return true;
@@ -2849,6 +2857,7 @@ static bool console_flush_all(bool do_cond_resched, u64 *next_seq, bool *handovebool any_usable = false;struct console *con;bool any_progress; +int cookie; *next_seq =0 ; *handover = false;
@@ -2856,23 +2865,29 @@ static bool console_flush_all(bool do_cond_resched, u64 *next_seq, bool *handove do { any_progress = false; - for_each_console(con) { + cookie = console_srcu_read_lock(); + for_each_console_srcu(con) { bool progress; if (!console_is_usable(con)) continue; any_usable = true; - if (con->flags & CON_EXTENDED) { + if (console_srcu_read_flags(con) & CON_EXTENDED) { /* Extended consoles do not print "dropped messages". */ progress = console_emit_next_record(con, &text[0], &ext_text[0], NULL, - handover); + handover, cookie); } else { progress = console_emit_next_record(con, &text[0], NULL, &dropped_text[0], - handover); + handover, cookie); } + + /* + * If a handover has occurred, the SRCU read lock + * is already released. + */ if (*handover) return false;
@@ -2886,14 +2901,19 @@ static bool console_flush_all(bool do_cond_resched, u64 *next_seq, bool *handove/* Allow panic_cpu to take over the consoles safely. */ if (abandon_console_lock_in_panic ()) -return false; + goto abandon;if (do_cond_resched)cond_resched (); } +console_srcu_read_unlock (cookie); }while (any_progress);return any_usable; + +abandon: +console_srcu_read_unlock (cookie); +return false; }/**
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 16/40 printk: __pr_flush: use srcu console list iterator
In reply to John OgnessUse srcu console list iteration for console list traversal.
Document why the console_lock is still necessary. Note that this is a preparatory change for when console_lock no longer provides synchronization for the console list.
--- kernel/printk/printk.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
kernel/printk/printk.c +9 -1
@@ -3560,6 +3560,7 @@ static bool __pr_flush(struct console *con, int timeout_ms, bool reset_on_progrestruct console *c;u64 last_diff =0 ;u64 printk_seq; +int cookie;u64 diff;u64 seq;
@@ -3570,9 +3571,15 @@ static bool __pr_flush(struct console *con, int timeout_ms, bool reset_on_progrefor (;;) { diff =0 ; +/* +* Hold the console_lock to guarantee safe access to +* console->seq and to prevent changes to @console_suspended +* until all consoles have been processed. +*/ console_lock (); -for_each_console (c) { + cookie =console_srcu_read_lock (); +for_each_console_srcu (c) {if (con && con != c)continue ;if (!console_is_usable (c))
@@ -3581,6 +3588,7 @@ static bool __pr_flush(struct console *con, int timeout_ms, bool reset_on_progreif (printk_seq < seq) diff += seq - printk_seq; } +console_srcu_read_unlock (cookie);/* * If consoles are suspended, it cannot be expected that they
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 17/40 printk: console_is_usable: use console_srcu_read_flags
In reply to John OgnessAll users of console_is_usable() are SRCU iterators. Use the appropriate wrapper function to locklessly read the flags.
--- kernel/printk/printk.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
kernel/printk/printk.c +5 -4
@@ -2708,11 +2708,13 @@ static bool abandon_console_lock_in_panic(void)* Check if the given console is currently capable and allowed to print * records. * -* Requires the console_lock. +* Requires the console_srcu_read_lock. */ static inline bool console_is_usable (struct console *con) { -if (!(con->flags &CON_ENABLED )) +short flags =console_srcu_read_flags (con); + +if (!(flags &CON_ENABLED ))return false;if (!con->write)
@@ -2723,8 +2725,7 @@ static inline bool console_is_usable(struct console *con)* allocated. So unless they're explicitly marked as being able to * cope (CON_ANYTIME) don't call them until this CPU is officially up. */ -if (!cpu_online (raw_smp_processor_id ()) && - !(con->flags &CON_ANYTIME )) +if (!cpu_online (raw_smp_processor_id ()) && !(flags &CON_ANYTIME ))return false;return true;
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 18/40 printk: console_unblank: use srcu console list iterator
In reply to John OgnessUse srcu console list iteration for console list traversal.
Document why the console_lock is still necessary. Note that this is a preparatory change for when console_lock no longer provides synchronization for the console list.
--- kernel/printk/printk.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-)
kernel/printk/printk.c +13 -4
@@ -2999,10 +2999,14 @@ EXPORT_SYMBOL(console_conditional_schedule);void console_unblank (void ) {struct console *c; +int cookie;/* -* console_unblank can no longer be called in interrupt context unless -* oops_in_progress is set to 1.. +* Stop console printing because the unblank() callback may +* assume the console is not within its write() callback. +* +* If @oops_in_progress is set, this may be an atomic context. +* In that case, attempt a trylock as best-effort. */ if (oops_in_progress) {if (down_trylock_console_sem () !=0 )
@@ -3012,9 +3016,14 @@ void console_unblank(void) console_locked =1 ; console_may_schedule =0 ; -for_each_console (c) -if ((c->flags &CON_ENABLED ) && c->unblank) + + cookie =console_srcu_read_lock (); +for_each_console_srcu (c) { +if ((console_srcu_read_flags (c) &CON_ENABLED ) && c->unblank) c->unblank (); + } +console_srcu_read_unlock (cookie); +console_unlock ();if (!oops_in_progress)
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 19/40 printk: console_flush_on_panic: use srcu console list iterator
In reply to John OgnessWith SRCU it is now safe to traverse the console list, even if the console_trylock() failed. However, overwriting console->seq when console_trylock() failed is still an issue.
Switch to SRCU iteration and document remaining issue with console->seq.
--- kernel/printk/printk.c | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-)
kernel/printk/printk.c +11 -10
@@ -3049,21 +3049,22 @@ void console_flush_on_panic(enum con_flush_mode mode) console_may_schedule =0 ;if (mode ==CONSOLE_REPLAY_ALL ) { -struct hlist_node *tmp;struct console *c; +int cookie;u64 seq; seq =prb_first_valid_seq (prb); -/* -* This cannot use for_each_console() because it's not established -* that the current context has console locked and neither there is -* a guarantee that there is no concurrency in that case. -* -* Open code it for documentation purposes and pretend that -* it works. -*/ -hlist_for_each_entry_safe (c, tmp, &console_list, node) + + cookie =console_srcu_read_lock (); +for_each_console_srcu (c) { +/* +* If the above console_trylock() failed, this is an +* unsynchronized assignment. But in that case, the +* kernel is in "hope and pray" mode anyway. +*/ c->seq = seq; + } +console_srcu_read_unlock (cookie); }console_unlock (); }
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 20/40 printk: console_device: use srcu console list iterator
In reply to John OgnessUse srcu console list iteration for console list traversal. It is acceptable because the consoles might come and go at any time. Strict synchronizing with console registration code would not bring any advantage over srcu.
Document why the console_lock is still necessary. Note that this is a preparatory change for when console_lock no longer provides synchronization for the console list.
--- kernel/printk/printk.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-)
kernel/printk/printk.c +11 -1
@@ -3076,15 +3076,25 @@ struct tty_driver *console_device(int *index) {struct console *c;struct tty_driver *driver =NULL ; +int cookie; +/* +* Take console_lock to serialize device() callback with +* other console operations. For example, fg_console is +* modified under console_lock when switching vt. +*/ console_lock (); -for_each_console (c) { + + cookie =console_srcu_read_lock (); +for_each_console_srcu (c) {if (!c->device)continue ; driver = c->device (c, index);if (driver)break ; } +console_srcu_read_unlock (cookie); +console_unlock ();return driver; }
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 21/40 console: introduce console_is_registered()
In reply to John OgnessCurrently it is not possible for drivers to detect if they have already successfully registered their console. Several drivers have multiple paths that lead to console registration. To avoid attempting a 2nd registration (which leads to a WARN), drivers are implementing their own solution.
Introduce console_is_registered() so drivers can easily identify if their console is currently registered. A _locked() variant is also provided if the caller is already holding the console_list_lock.
--- include/linux/console.h | 28 ++++++++++++++++++++++++++++ kernel/printk/printk.c | 2 +- 2 files changed, 29 insertions(+), 1 deletion(-)
include/linux/console.h +28 -0
@@ -228,6 +228,34 @@ static inline void console_srcu_write_flags(struct console *con, short flags)WRITE_ONCE (con->flags, flags); } +/* Variant of console_is_registered() when the console_list_lock is held. */ +static inline bool console_is_registered_locked (const struct console *con) +{ +lockdep_assert_console_list_lock_held (); +return !hlist_unhashed (&con->node); +} + +/* +* console_is_registered - Check if the console is registered +* @con: struct console pointer of console to check +* +* Context: Process context. May sleep while acquiring console list lock. +* Return: true if the console is in the console list, otherwise false. +* +* If false is returned for a console that was previously registered, it +* can be assumed that the console's unregistration is fully completed, +* including the exit() callback after console list removal. +*/ +static inline bool console_is_registered (const struct console *con) +{ +bool ret; + +console_list_lock (); + ret =console_is_registered_locked (con); +console_list_unlock (); +return ret; +} +/** * for_each_console_srcu() - Iterator over registered consoles * @con: struct console pointer used as loop cursor
kernel/printk/printk.c +1 -1
@@ -3442,7 +3442,7 @@ static int unregister_console_locked(struct console *console)/* Disable it unconditionally */ console_srcu_write_flags (console, console->flags & ~CON_ENABLED ); -if (hlist_unhashed (&console->node)) { +if (!console_is_registered_locked (console)) {console_unlock ();return -ENODEV ; }
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 22/40 serial_core: replace uart_console_enabled() with uart_console_registered()
In reply to John OgnessAll users of uart_console_enabled() really want to know if a console is registered. It is not reliable to check for CON_ENABLED in order to identify if a console is registered. Use console_is_registered() instead.
A _locked() variant is provided because uart_set_options() is always called with the console_list_lock held and must check if a console is registered in order to synchronize with kgdboc.
--- drivers/tty/serial/8250/8250_core.c | 2 +- drivers/tty/serial/pic32_uart.c | 2 +- drivers/tty/serial/serial_core.c | 14 +++++++------- include/linux/serial_core.h | 10 ++++++++-- 4 files changed, 17 insertions(+), 11 deletions(-)
drivers/tty/serial/8250/8250_core.c +1 -1
@@ -565,7 +565,7 @@ serial8250_register_ports(struct uart_driver *drv, struct device *dev) up->port.dev = dev; -if (uart_console_enabled (&up->port)) +if (uart_console_registered (&up->port))pm_runtime_get_sync (up->port.dev);serial8250_apply_quirks (up);
drivers/tty/serial/pic32_uart.c +1 -1
@@ -919,7 +919,7 @@ static int pic32_uart_probe(struct platform_device *pdev) }#ifdef CONFIG_SERIAL_PIC32_CONSOLE -if (uart_console_enabled (port)) { +if (uart_console_registered (port)) {/* The peripheral clock has been enabled by console_setup, * so disable it till the port is used. */
drivers/tty/serial/serial_core.c +7 -7
@@ -2223,11 +2223,11 @@ uart_set_options(struct uart_port *port, struct console *co,/* * Ensure that the serial-console lock is initialised early. * -* Note that the console-enabled check is needed because of kgdboc, -* which can end up calling uart_set_options() for an already enabled +* Note that the console-registered check is needed because +* kgdboc can call uart_set_options() for an already registered * console via tty_find_polling_driver() and uart_poll_init(). */ -if (!uart_console_enabled (port) && !port->console_reinit) +if (!uart_console_registered_locked (port) && !port->console_reinit)uart_port_spin_lock_init (port);memset (&termios,0 ,sizeof (struct ktermios ));
@@ -2573,7 +2573,7 @@ uart_configure_port(struct uart_driver *drv, struct uart_state *state,* successfully registered yet, try to re-register it. * It may be that the port was not available. */ -if (port->cons && !(port->cons->flags &CON_ENABLED )) +if (port->cons && !console_is_registered (port->cons))register_console (port->cons);/*
@@ -2956,7 +2956,7 @@ static ssize_t console_show(struct device *dev,mutex_lock (&port->mutex); uport =uart_port_check (state);if (uport) - console =uart_console_enabled (uport); + console =uart_console_registered (uport);mutex_unlock (&port->mutex);return sprintf (buf,"%c\n" , console ?'Y' :'N' );
@@ -2978,7 +2978,7 @@ static ssize_t console_store(struct device *dev,mutex_lock (&port->mutex); uport =uart_port_check (state);if (uport) { - oldconsole =uart_console_enabled (uport); + oldconsole =uart_console_registered (uport);if (oldconsole && !newconsole) { ret =unregister_console (uport->cons); }else if (!oldconsole && newconsole) {
@@ -3086,7 +3086,7 @@ int uart_add_one_port(struct uart_driver *drv, struct uart_port *uport)* If this port is in use as a console then the spinlock is already * initialised. */ -if (!uart_console_enabled (uport)) +if (!uart_console_registered (uport))uart_port_spin_lock_init (uport);if (uport->cons && uport->dev)
include/linux/serial_core.h +8 -2
@@ -743,9 +743,15 @@ static const bool earlycon_acpi_spcr_enable EARLYCON_USED_OR_UNUSED;static inline int setup_earlycon (char *buf) {return 0 ; }#endif -static inline bool uart_console_enabled (struct uart_port *port) +/* Variant of uart_console_registered() when the console_list_lock is held. */ +static inline bool uart_console_registered_locked (struct uart_port *port) { -return uart_console (port) && (port->cons->flags &CON_ENABLED ); +return uart_console (port) &&console_is_registered_locked (port->cons); +} + +static inline bool uart_console_registered (struct uart_port *port) +{ +return uart_console (port) &&console_is_registered (port->cons); } struct uart_port *uart_get_console(struct uart_port *ports, int nr,
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 23/40 tty: nfcon: use console_is_registered()
In reply to John OgnessCurrently CON_ENABLED is being (mis)used to identify if the console has been registered. This is not reliable because it can be set even though registration failed or it can be unset, even though the console is registered. Use console_is_registered() instead.
--- arch/m68k/emu/nfcon.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
arch/m68k/emu/nfcon.c +7 -2
@@ -49,7 +49,7 @@ static void nfcon_write(struct console *con, const char *str,static struct tty_driver *nfcon_device (struct console *con,int *index) { *index =0 ; -return (con->flags &CON_ENABLED ) ? nfcon_tty_driver :NULL ; +return console_is_registered (con) ? nfcon_tty_driver :NULL ; }static struct console nf_console = {
@@ -107,6 +107,11 @@ static int __init nf_debug_setup(char *arg) stderr_id =nf_get_id ("NF_STDERR" );if (stderr_id) { +/* +* The console will be enabled when debug=nfcon is specified +* as a kernel parameter. Since this is a non-standard way +* of enabling consoles, it must be explicitly enabled. +*/ nf_console.flags |=CON_ENABLED ;register_console (&nf_console); }
@@ -151,7 +156,7 @@ static int __init nfcon_init(void) nfcon_tty_driver = driver; -if (!(nf_console.flags &CON_ENABLED )) +if (!console_is_registered (&nf_console))register_console (&nf_console);return 0 ;
Signature · 1 line
2.30.2
Re: [PATCH printk v5 23/40] tty: nfcon: use console_is_registered()
Quoted 7 lines · John Ogness
Currently
CON_ENABLEDis being (mis)used to identify if the console has been registered. This is not reliable because it can be set even though registration failed or it can be unset, even though the console is registered. Useconsole_is_registered()instead.Signed-off-by John Ogness <[email protected]>Reviewed-by Petr Mladek <[email protected]>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
John Ogness
maintainerPATCH v5 24/40 efi: earlycon: use console_is_registered()
In reply to John OgnessThe CON_ENABLED status of a console is a runtime setting that does not involve the console driver. Drivers must not assume that if the console is disabled then proper hardware management is not needed. For the EFI earlycon case, it is about remapping/unmapping memory for the framebuffer.
Use console_is_registered() instead of checking CON_ENABLED.
--- drivers/firmware/efi/earlycon.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/firmware/efi/earlycon.c +4 -4
@@ -29,8 +29,8 @@ static void *efi_fb;*/ static int __init efi_earlycon_remap_fb (void ) { -/* bail if there is no bootconsole or it has been disabled already */ -if (!earlycon_console || !(earlycon_console->flags &CON_ENABLED )) +/* bail if there is no bootconsole or it was unregistered already */ +if (!earlycon_console || !console_is_registered (earlycon_console))return 0 ; efi_fb = memremap(fb_base, screen_info.lfb_size,
@@ -42,8 +42,8 @@ early_initcall(efi_earlycon_remap_fb);static int __init efi_earlycon_unmap_fb (void ) { -/* unmap the bootconsole fb unless keep_bootcon has left it enabled */ -if (efi_fb && !(earlycon_console->flags &CON_ENABLED )) +/* unmap the bootconsole fb unless keep_bootcon left it registered */ +if (efi_fb && !console_is_registered (earlycon_console))memunmap (efi_fb);return 0 ; }
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 25/40 tty: hvc: use console_is_registered()
In reply to John OgnessIt is not reliable to check for CON_ENABLED in order to identify if a console is registered. Use console_is_registered() instead.
--- drivers/tty/hvc/hvc_console.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/tty/hvc/hvc_console.c +2 -2
@@ -264,8 +264,8 @@ static void hvc_port_destruct(struct tty_port *port)static void hvc_check_console (int index) { -/* Already enabled, bail out */ -if (hvc_console.flags &CON_ENABLED ) +/* Already registered, bail out */ +if (console_is_registered (&hvc_console))return ;/* If this index is what the user requested, then register
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 26/40 tty: serial: earlycon: use console_is_registered()
In reply to John OgnessIt is not reliable to check for CON_ENABLED in order to identify if a console is registered. Use console_is_registered() instead.
--- drivers/tty/serial/earlycon.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/tty/serial/earlycon.c +2 -2
@@ -181,7 +181,7 @@ int __init setup_earlycon(char *buf)if (!buf || !buf[0 ])return -EINVAL ; -if (early_con.flags &CON_ENABLED ) +if (console_is_registered (&early_con))return -EALREADY ; again:
@@ -253,7 +253,7 @@ int __init of_setup_earlycon(const struct earlycon_id *match,bool big_endian;u64 addr; -if (early_con.flags &CON_ENABLED ) +if (console_is_registered (&early_con))return -EALREADY ;spin_lock_init (&port->lock);
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 27/40 tty: serial: pic32_uart: use console_is_registered()
In reply to John OgnessIt is not reliable to check for CON_ENABLED in order to identify if a console is registered. Use console_is_registered() instead.
--- drivers/tty/serial/pic32_uart.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/tty/serial/pic32_uart.c +1 -1
@@ -843,7 +843,7 @@ console_initcall(pic32_console_init);*/ static int __init pic32_late_console_init (void ) { -if (!(pic32_console.flags &CON_ENABLED )) +if (!console_is_registered (&pic32_console))register_console (&pic32_console);return 0 ;
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 28/40 tty: serial: samsung_tty: use console_is_registered()
In reply to John OgnessIt is not reliable to check for CON_ENABLED in order to identify if a console is registered. Use console_is_registered() instead.
--- drivers/tty/serial/samsung_tty.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/tty/serial/samsung_tty.c +1 -1
@@ -1732,7 +1732,7 @@ static void __init s3c24xx_serial_register_console(void)static void s3c24xx_serial_unregister_console (void ) { -if (s3c24xx_serial_console.flags &CON_ENABLED ) +if (console_is_registered (&s3c24xx_serial_console))unregister_console (&s3c24xx_serial_console); }
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 29/40 tty: serial: xilinx_uartps: use console_is_registered()
In reply to John OgnessIt is not reliable to check for CON_ENABLED in order to identify if a console is registered. Use console_is_registered() instead.
--- drivers/tty/serial/xilinx_uartps.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/tty/serial/xilinx_uartps.c +1 -1
@@ -1631,7 +1631,7 @@ static int cdns_uart_probe(struct platform_device *pdev)#ifdef CONFIG_SERIAL_XILINX_PS_UART_CONSOLE /* This is not port which is used for console that's why clean it up */ if (console_port == port && - !(cdns_uart_uart_driver.cons->flags &CON_ENABLED )) { + !console_is_registered (cdns_uart_uart_driver.cons)) { console_port =NULL ; cdns_uart_console.index =-1 ; }
Signature · 7 lines
2.30.2 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
John Ogness
maintainerPATCH v5 30/40 usb: early: xhci-dbc: use console_is_registered()
In reply to John OgnessIt is not reliable to check for CON_ENABLED in order to identify if a console is registered. Use console_is_registered() instead.
--- drivers/usb/early/xhci-dbc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/early/xhci-dbc.c +1 -1
@@ -927,7 +927,7 @@ void __init early_xdbc_register_console(void)static void xdbc_unregister_console (void ) { -if (early_xdbc_console.flags &CON_ENABLED ) +if (console_is_registered (&early_xdbc_console))unregister_console (&early_xdbc_console); }
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 31/40 netconsole: avoid CON_ENABLED misuse to track registration
In reply to John OgnessThe CON_ENABLED flag is being misused to track whether or not the extended console should be or has been registered. Instead use a local variable to decide if the extended console should be registered and console_is_registered() to determine if it has been registered.
Also add a check in cleanup_netconsole() to only unregister the extended console if it has been registered.
--- drivers/net/netconsole.c | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-)
drivers/net/netconsole.c +11 -10
@@ -332,10 +332,8 @@ static ssize_t enabled_store(struct config_item *item, }if (enabled) {/* true */ -if (nt->extended && !(netconsole_ext.flags &CON_ENABLED )) { - netconsole_ext.flags |=CON_ENABLED ; +if (nt->extended && !console_is_registered (&netconsole_ext))register_console (&netconsole_ext); - }/* * Skip netpoll_parse_options() -- all the attributes are
@@ -869,7 +867,7 @@ static void write_msg(struct console *con, const char *msg, unsigned int len)static struct console netconsole_ext = { .name ="netcon_ext" , - .flags =CON_EXTENDED ,/* starts disabled, registered on first use */ + .flags =CON_ENABLED |CON_EXTENDED , .write = write_ext_msg, };
@@ -883,6 +881,7 @@ static int __init init_netconsole(void) {int err;struct netconsole_target *nt, *tmp; +bool extended = false;unsigned long flags;char *target_config;char *input = config;
@@ -895,11 +894,12 @@ static int __init init_netconsole(void) goto fail; }/* Dump existing printks when we register */ -if (nt->extended) - netconsole_ext.flags |=CON_PRINTBUFFER | -CON_ENABLED ; -else +if (nt->extended) { + extended = true; + netconsole_ext.flags |=CON_PRINTBUFFER ; + }else { netconsole.flags |=CON_PRINTBUFFER ; + }spin_lock_irqsave (&target_list_lock, flags);list_add (&nt->list, &target_list);
@@ -915,7 +915,7 @@ static int __init init_netconsole(void)if (err) goto undonotifier; -if (netconsole_ext.flags &CON_ENABLED ) +if (extended)register_console (&netconsole_ext);register_console (&netconsole);pr_info ("network logging started\n" );
@@ -945,7 +945,8 @@ static void __exit cleanup_netconsole(void) {struct netconsole_target *nt, *tmp; -unregister_console (&netconsole_ext); +if (console_is_registered (&netconsole_ext)) +unregister_console (&netconsole_ext);unregister_console (&netconsole);dynamic_netconsole_exit ();unregister_netdevice_notifier (&netconsole_netdev_notifier);
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 32/40 printk, xen: fbfront: create/use safe function for forcing preferred
In reply to John OgnessWith commit 9e124fe16ff2("xen: Enable console tty by default in domU if it's not a dummy") a hack was implemented to make sure that the tty console remains the console behind the /dev/console device. The main problem with the hack is that, after getting the console pointer to the tty console, it is assumed the pointer is still valid after releasing the console_sem. This assumption is incorrect and unsafe.
Make the hack safe by introducing a new function console_force_preferred_locked() and perform the full operation under the console_list_lock.
--- drivers/video/fbdev/xen-fbfront.c | 12 +++----- include/linux/console.h | 1 + kernel/printk/printk.c | 49 +++++++++++++++++++++++++++++-- 3 files changed, 51 insertions(+), 11 deletions(-)
drivers/video/fbdev/xen-fbfront.c +4 -8
@@ -504,18 +504,14 @@ static void xenfb_make_preferred_console(void)if (console_set_on_cmdline)return ; -console_lock (); +console_list_lock ();for_each_console (c) {if (!strcmp (c->name,"tty" ) && c->index ==0 )break ; } -console_unlock (); -if (c) { -unregister_console (c); - c->flags |=CON_CONSDEV ; - c->flags &= ~CON_PRINTBUFFER ;/* don't print again */ -register_console (c); - } +if (c) +console_force_preferred_locked (c); +console_list_unlock (); }static int xenfb_resume (struct xenbus_device *dev)
include/linux/console.h +1 -0
@@ -291,6 +291,7 @@ enum con_flush_mode { };extern int add_preferred_console (char *name,int idx,char *options); +extern void console_force_preferred_locked (struct console *con);extern void register_console (struct console *);extern int unregister_console (struct console *);extern void console_lock (void );
kernel/printk/printk.c +46 -3
61 lines not on this page · raw message
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 33/40 tty: tty_io: use console_list_lock for list synchronization
In reply to John Ognessshow_cons_active() uses the console_lock to gather information on registered consoles. It requires that no consoles are unregistered until it is finished. The console_list_lock should be used because list synchronization responsibility will be removed from the console_lock in a later change.
Note, the console_lock is still needed to serialize the device() callback with other console operations.
--- drivers/tty/tty_io.c | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-)
drivers/tty/tty_io.c +12 -6
@@ -3527,16 +3527,13 @@ static ssize_t show_cons_active(struct device *dev,ssize_t count =0 ;/* -* Hold the console_lock to guarantee that no consoles are +* Hold the console_list_lock to guarantee that no consoles are * unregistered until all console processing is complete. * This also allows safe traversal of the console list and * race-free reading of @flags. -* -* Take console_lock to serialize device() callback with -* other console operations. For example, fg_console is -* modified under console_lock when switching vt. */ -console_lock (); +console_list_lock (); +for_each_console (c) {if (!c->device)continue ;
@@ -3548,6 +3545,13 @@ static ssize_t show_cons_active(struct device *dev,if (i >=ARRAY_SIZE (cs))break ; } + +/* +* Take console_lock to serialize device() callback with +* other console operations. For example, fg_console is +* modified under console_lock when switching vt. +*/ +console_lock ();while (i--) {int index = cs[i]->index;struct tty_driver *drv = cs[i]->device (cs[i], &index);
@@ -3563,6 +3567,8 @@ static ssize_t show_cons_active(struct device *dev, }console_unlock (); +console_list_unlock (); +return count; } static DEVICE_ATTR(active, S_IRUGO, show_cons_active, NULL);
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 34/40 proc: consoles: use console_list_lock for list iteration
In reply to John OgnessThe console_lock is used in part to guarantee safe list iteration. The console_list_lock should be used because list synchronization responsibility will be removed from the console_lock in a later change.
Note, the console_lock is still needed to serialize the device() callback with other console operations.
--- fs/proc/consoles.c | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-)
fs/proc/consoles.c +12 -7
@@ -33,7 +33,16 @@ static int show_console_dev(struct seq_file *m, void *v)if (con->device) {const struct tty_driver *driver;int index; + +/* +* Take console_lock to serialize device() callback with +* other console operations. For example, fg_console is +* modified under console_lock when switching vt. +*/ +console_lock (); driver = con->device (con, &index); +console_unlock (); +if (driver) { dev =MKDEV (driver->major, driver->minor_start); dev += index;
@@ -64,15 +73,11 @@ static void *c_start(struct seq_file *m, loff_t *pos)loff_t off =0 ;/* -* Take console_lock to serialize device() callback with -* other console operations. For example, fg_console is -* modified under console_lock when switching vt. -* -* Hold the console_lock to guarantee safe traversal of the +* Hold the console_list_lock to guarantee safe traversal of the * console list. SRCU cannot be used because there is no * place to store the SRCU cookie. */ -console_lock (); +console_list_lock ();for_each_console (con)if (off++ == *pos)break ;
@@ -90,7 +95,7 @@ static void *c_next(struct seq_file *m, void *v, loff_t *pos)static void c_stop (struct seq_file *m,void *v) { -console_unlock (); +console_list_unlock (); }static const struct seq_operations consoles_op = {
Signature · 1 line
2.30.2
John Ogness
maintainerPATCH v5 35/40 tty: serial: kgdboc: use srcu console list iterator
In reply to John OgnessUse srcu console list iteration for safe console list traversal. Note that this is a preparatory change for when console_lock no longer provides synchronization for the console list.
--- drivers/tty/serial/kgdboc.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
drivers/tty/serial/kgdboc.c +8 -2
@@ -451,6 +451,7 @@ static void kgdboc_earlycon_pre_exp_handler(void) {struct console *con;static bool already_warned; +int cookie;if (already_warned)return ;
@@ -463,9 +464,14 @@ static void kgdboc_earlycon_pre_exp_handler(void)* serial drivers might be OK with this, print a warning once per * boot if we detect this case. */ -for_each_console (con) + cookie =console_srcu_read_lock (); +for_each_console_srcu (con) {if (con == kgdboc_earlycon_io_ops.cons) -return ; +break ; + } +console_srcu_read_unlock (cookie); +if (con) +return ; already_warned = true;pr_warn ("kgdboc_earlycon is still using bootconsole\n" );
Signature · 1 line
2.30.2
Re: [PATCH printk v5 35/40] tty: serial: kgdboc: use srcu console list iterator
Hi,
Quoted 27 lines · John Ogness
Use srcu console list iteration for safe console list traversal. Note that this is a preparatory change for when
console_lockno longer provides synchronization for the console list.Signed-off-by John Ogness <[email protected]>Reviewed-by Petr Mladek <[email protected]>--- drivers/tty/serial/kgdboc.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)drivers/tty/serial/kgdboc.c +1
-0@@ -451,6 +451,7 @@ static void kgdboc_earlycon_pre_exp_handler(void) {struct console *con;static bool already_warned; +int cookie;if (already_warned)return ;@@ -463,9 +464,14 @@ static void kgdboc_earlycon_pre_exp_handler(void)* serial drivers might be OK with this, print a warning once per * boot if we detect this case. */
drivers/tty/serial/kgdboc.c static void kgdboc_earlycon_pre_exp_handler(void) · line 474
Quoted 10 lines
drivers/tty/serial/kgdboc.c +7
-2-for_each_console (con) + cookie =console_srcu_read_lock (); +for_each_console_srcu (con) {if (con == kgdboc_earlycon_io_ops.cons) -return ; +break ; + } +console_srcu_read_unlock (cookie); +if (con) +return ;
Is there truly any guarantee that "con" will be NULL if for_each_console_srcu() finishes naturally (AKA without a "break" being executed)?
It looks as if currently this will be true but nothing in the comments of for_each_console_srcu() nor hlist_for_each_entry_srcu() (which it calls) guarantees this, right? It would be nice if that was documented, but I guess it's not a huge deal.
Also: wasn't there just some big issue about people using loop
iteration variables after the loop finished?
https://lwn.net/Articles/885941/
Ah, I guess that's a slightly different problem and probably not relevant here.
So it seems like this is fine.
John Ogness
maintainerRe: [PATCH printk v5 35/40] tty: serial: kgdboc: use srcu console list iterator
Hi Doug,
Quoted 10 lines · Doug Anderson
Quoted 10 lines
drivers/tty/serial/kgdboc.c +3
-2@@ -463,9 +464,14 @@ static void kgdboc_earlycon_pre_exp_handler(void)* serial drivers might be OK with this, print a warning once per * boot if we detect this case. */ -for_each_console (con) + cookie =console_srcu_read_lock (); +for_each_console_srcu (con) {if (con == kgdboc_earlycon_io_ops.cons) -return ; +break ;
Quoted 8 lines
drivers/tty/serial/kgdboc.c static void kgdboc_earlycon_pre_exp_handler(void) · line 474
Quoted 4 lines
drivers/tty/serial/kgdboc.c +4
-0+ } +console_srcu_read_unlock (cookie); +if (con) +return ;Is there truly any guarantee that "con" will be NULL if
for_each_console_srcu()finishes naturally (AKA without a "break" being executed)?
Right now it is true because @con becoming NULL is the exit criteria for the loop.
Quoted 4 lines
It looks as if currently this will be true but nothing in the comments of
for_each_console_srcu()norhlist_for_each_entry_srcu()(which it calls) guarantees this, right? It would be nice if that was documented, but I guess it's not a huge deal.
Yes, if it is frowned upon that the iterator is used outside the loop, it would be nice if the for_each macros explicitly provided some hints in their documentation.
Quoted 4 lines
Also: wasn't there just some big issue about people using loop iteration variables after the loop finished?
Thanks for referencing that article! Indeed if the macros are changed so that the iterator is defined in the loop, then code like this will break. But I would expect that making such macro changes will also require updating the call sites to avoid unused variables outside the loops. And then this code could receive the appropriate fixup.
I feel like if I add extra code to guarantee a NULL without relying on the macro implementation, I'll get more resistance due to unnecessarily adding code and variables. But I may be wrong.
Quoted 1 line
Reviewed-by Douglas Anderson <[email protected]>
Thanks.
John
John Ogness
maintainerPATCH v5 36/40 tty: serial: kgdboc: use console_list_lock for list traversal
In reply to John Ognessconfigure_kgdboc() uses the console_lock for console list iteration. Use the console_list_lock instead because list synchronization responsibility will be removed from the console_lock in a later change.
The SRCU iterator could have been used here, but a later change will relocate the locking of the console_list_lock to also provide synchronization against register_console().
Note, the console_lock is still needed to serialize the device() callback with other console operations.
--- drivers/tty/serial/kgdboc.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/tty/serial/kgdboc.c +12 -0
@@ -193,7 +193,16 @@ static int configure_kgdboc(void)if (!p) goto noconfig; +/* For safe traversal of the console list. */ +console_list_lock (); + +/* +* Take console_lock to serialize device() callback with +* other console operations. For example, fg_console is +* modified under console_lock when switching vt. +*/ console_lock (); +for_each_console (cons) {int idx; if (cons->device && cons->device(cons, &idx) == p &&
@@ -202,8 +211,11 @@ static int configure_kgdboc(void)break ; } } +console_unlock (); +console_list_unlock (); + kgdb_tty_driver = p; kgdb_tty_line = tty_line;
Signature · 1 line
2.30.2
Re: [PATCH printk v5 36/40] tty: serial: kgdboc: use console_list_lock for list traversal
Hi,
Quoted 9 lines · John Ogness
configure_kgdboc()uses theconsole_lockfor console list iteration. Use theconsole_list_lockinstead because list synchronization responsibility will be removed from theconsole_lockin a later change.The SRCU iterator could have been used here, but a later change will relocate the locking of the
console_list_lockto also provide synchronization againstregister_console().
Quoted 8 lines
Note, the
console_lockis still needed to serialize thedevice()callback with other console operations.Signed-off-by John Ogness <[email protected]>Reviewed-by Petr Mladek <[email protected]>--- drivers/tty/serial/kgdboc.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
John Ogness
maintainerPATCH v5 37/40 tty: serial: kgdboc: synchronize tty_find_polling_driver() and register_console()
In reply to John OgnessCalling tty_find_polling_driver() can lead to uart_set_options() being called (via the poll_init() callback of tty_operations) to configure the uart. But uart_set_options() can also be called by register_console() (via the setup() callback of console).
Take the console_list_lock to synchronize against register_console() and also use it for console list traversal. This also ensures the console list cannot change until the polling console has been chosen.
--- drivers/tty/serial/kgdboc.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
drivers/tty/serial/kgdboc.c +12 -4
@@ -189,12 +189,20 @@ static int configure_kgdboc(void)if (kgdboc_register_kbd (&cptr)) goto do_register; +/* +* tty_find_polling_driver() can call uart_set_options() +* (via poll_init) to configure the uart. Take the console_list_lock +* in order to synchronize against register_console(), which can also +* configure the uart via uart_set_options(). This also allows safe +* traversal of the console list. +*/ +console_list_lock (); + p =tty_find_polling_driver (cptr, &tty_line); -if (!p) +if (!p) { +console_list_unlock (); goto noconfig; - -/* For safe traversal of the console list. */ -console_list_lock (); + }/* * Take console_lock to serialize device() callback with
Signature · 1 line
2.30.2
Re: [PATCH printk v5 37/40] tty: serial: kgdboc: synchronize tty_find_polling_driver() and register_console()
Hi,
Quoted 33 lines · John Ogness
Calling
tty_find_polling_driver()can lead touart_set_options()being called (via thepoll_init()callback oftty_operations) to configure the uart. Butuart_set_options()can also be called byregister_console()(via thesetup()callback of console).Take the
console_list_lockto synchronize againstregister_console()and also use it for console list traversal. This also ensures the console list cannot change until the polling console has been chosen.Signed-off-by John Ogness <[email protected]>Reviewed-by Daniel Thompson <[email protected]>Reviewed-by Petr Mladek <[email protected]>--- drivers/tty/serial/kgdboc.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)drivers/tty/serial/kgdboc.c +8
-0@@ -189,12 +189,20 @@ static int configure_kgdboc(void)if (kgdboc_register_kbd (&cptr)) goto do_register; +/* +* tty_find_polling_driver() can call uart_set_options() +* (via poll_init) to configure the uart. Take the console_list_lock +* in order to synchronize against register_console(), which can also +* configure the uart via uart_set_options(). This also allows safe +* traversal of the console list. +*/ +console_list_lock ();
drivers/tty/serial/kgdboc.c static int configure_kgdboc(void) · line 205
Quoted 10 lines
drivers/tty/serial/kgdboc.c +4
-4+ p =tty_find_polling_driver (cptr, &tty_line); -if (!p) +if (!p) { +console_list_unlock (); goto noconfig; - -/* For safe traversal of the console list. */ -console_list_lock (); + }
Seems OK to me, though I guess I would have moved console_lock() up too just because this isn't a case we need to optimize and then we can be extra certain that nobody else is messing with console structures while we're looking at them.
John Ogness
maintainerRe: [PATCH printk v5 37/40] tty: serial: kgdboc: synchronize tty_find_polling_driver() and register_console()
Quoted 4 lines · Doug Anderson
Seems OK to me, though I guess I would have moved
console_lock()up too just because this isn't a case we need to optimize and then we can be extra certain that nobody else is messing with console structures while we're looking at them.
Actually this series is not about optimization. It is about reducing the scope of console_lock and removing unnecessary use of it.
If tty_find_polling_driver() needs to be called under the console_lock, then we need to document exactly why. I could not find any situations where it is necessary.
Also keep in mind that in the long term we will be completely removing the console_lock. It is a painful process of identifying and dismantling its scope and replacing it with multiple clearly scoped locking mechanisms.
Quoted 1 line
Reviewed-by Douglas Anderson <[email protected]>
Thanks.
John
John Ogness
maintainerPATCH v5 38/40 tty: serial: kgdboc: use console_list_lock to trap exit
In reply to John Ognesskgdboc_earlycon_init() uses the console_lock to ensure that no consoles are unregistered until the kgdboc_earlycon is setup. The console_list_lock should be used instead because list synchronization responsibility will be removed from the console_lock in a later change.
--- drivers/tty/serial/kgdboc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/tty/serial/kgdboc.c +3 -3
@@ -558,13 +558,13 @@ static int __init kgdboc_earlycon_init(char *opt)*/ /* -* Hold the console_lock to guarantee that no consoles are +* Hold the console_list_lock to guarantee that no consoles are * unregistered until the kgdboc_earlycon setup is complete. * Trapping the exit() callback relies on exit() not being * called until the trap is setup. This also allows safe * traversal of the console list and race-free reading of @flags. */ -console_lock (); +console_list_lock ();for_each_console (con) { if (con->write && con->read && (con->flags & (CON_BOOT | CON_ENABLED)) &&
@@ -606,7 +606,7 @@ static int __init kgdboc_earlycon_init(char *opt) } unlock: -console_unlock (); +console_list_unlock ();/* Non-zero means malformed option so we always return zero */ return 0 ;
Signature · 1 line
2.30.2
Doug Anderson
reviewerRe: [PATCH printk v5 38/40] tty: serial: kgdboc: use console_list_lock to trap exit
Hi,
Quoted 23 lines · John Ogness
kgdboc_earlycon_init()uses theconsole_lockto ensure that no consoles are unregistered until thekgdboc_earlyconis setup. Theconsole_list_lockshould be used instead because list synchronization responsibility will be removed from theconsole_lockin a later change.Signed-off-by John Ogness <[email protected]>Reviewed-by Daniel Thompson <[email protected]>Reviewed-by Petr Mladek <[email protected]>--- drivers/tty/serial/kgdboc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)drivers/tty/serial/kgdboc.c +1
-1@@ -558,13 +558,13 @@ static int __init kgdboc_earlycon_init(char *opt)*/ /* -* Hold the console_lock to guarantee that no consoles are +* Hold the console_list_lock to guarantee that no consoles are
drivers/tty/serial/kgdboc.c static int __init kgdboc_earlycon_init(char *opt) · line 570
Quoted 10 lines
drivers/tty/serial/kgdboc.c +1
-1* unregistered until the kgdboc_earlycon setup is complete. * Trapping the exit() callback relies on exit() not being * called until the trap is setup. This also allows safe * traversal of the console list and race-free reading of @flags. */ -console_lock (); +console_list_lock ();for_each_console (con) { if (con->write && con->read && (con->flags & (CON_BOOT | CON_ENABLED)) &&
Officially don't we need both the list lock and normal lock here since we're reaching into the consoles?
-Doug
John Ogness
maintainerRe: [PATCH printk v5 38/40] tty: serial: kgdboc: use console_list_lock to trap exit
Quoted 14 lines · Doug Anderson
drivers/tty/serial/kgdboc.c static int __init kgdboc_earlycon_init(char *opt) · line 570
Quoted 13 lines
/*drivers/tty/serial/kgdboc.c +2
-2-* Hold the console_lock to guarantee that no consoles are +* Hold the console_list_lock to guarantee that no consoles are * unregistered until the kgdboc_earlycon setup is complete. * Trapping the exit() callback relies on exit() not being * called until the trap is setup. This also allows safe * traversal of the console list and race-free reading of @flags. */ -console_lock (); +console_list_lock ();for_each_console (con) { if (con->write && con->read && (con->flags & (CON_BOOT | CON_ENABLED)) &&
Quoted 2 lines
Officially don't we need both the list lock and normal lock here since we're reaching into the consoles?
AFAICT the only synchronization we need here is iterating the console list, reading con->flags of a registered console, and modifying con->exit of a registered console. The console_list_lock provides synchronization for all of these things. By the end of this series the console_lock does not provide synchronization for any of these things.
Is there something else that requires synchronization here?
After this series the console_lock is still responsible for:
- serializing console->write() callbacks
- stopping console->write() callbacks
- stopping console->device() callbacks
- synchronizing console->seq
- synchronizing console->dropped
- synchronizing the global @console_suspended
- providing various unclear protection for vt consoles
- some bizarre misuses in bcache
The scope may be larger than the above list. The investigation is still ongoing.
John
John Ogness
maintainerPATCH v5 39/40 printk: relieve console_lock of list synchronization duties
In reply to John OgnessThe console_list_lock provides synchronization for console list and console->flags updates. All call sites that were using the console_lock for this synchronization have either switched to use the console_list_lock or the SRCU list iterator.
Remove console_lock usage for console list updates and console->flags updates.
--- kernel/printk/printk.c | 44 +++++++++++++++++++----------------------- 1 file changed, 20 insertions(+), 24 deletions(-)
kernel/printk/printk.c +20 -24
@@ -86,8 +86,8 @@ EXPORT_SYMBOL(oops_in_progress);static DEFINE_MUTEX (console_mutex);/* -* console_sem protects console_list and console->flags updates, and also -* provides serialization for access to the entire console driver system. +* console_sem protects updates to console->seq and console_suspended, +* and also provides serialization for console printing. */ static DEFINE_SEMAPHORE (console_sem);HLIST_HEAD (console_list);
@@ -2639,10 +2639,10 @@ static int console_cpu_notify(unsigned int cpu) }/** -* console_lock - lock the console system for exclusive use. +* console_lock - block the console subsystem from printing * -* Acquires a lock which guarantees that the caller has -* exclusive access to the console system and console_list. +* Acquires a lock which guarantees that no consoles will +* be in or enter their write() callback. * * Can sleep, returns nothing. */
@@ -2659,10 +2659,10 @@ void console_lock(void)EXPORT_SYMBOL (console_lock);/** -* console_trylock - try to lock the console system for exclusive use. +* console_trylock - try to block the console subsystem from printing * -* Try to acquire a lock which guarantees that the caller has exclusive -* access to the console system and console_list. +* Try to acquire a lock which guarantees that no consoles will +* be in or enter their write() callback. * * returns 1 on success, and 0 on failure to acquire the lock. */
@@ -2919,10 +2919,10 @@ static bool console_flush_all(bool do_cond_resched, u64 *next_seq, bool *handove }/** -* console_unlock - unlock the console system +* console_unlock - unblock the console subsystem from printing * -* Releases the console_lock which the caller holds on the console system -* and the console driver list. +* Releases the console_lock which the caller holds to block printing of +* the console subsystem. * * While the console_lock was held, console output may have been buffered * by printk(). If this is the case, console_unlock(); emits
@@ -3109,9 +3109,7 @@ void console_stop(struct console *console) {__pr_flush (console,1000 , true);console_list_lock (); -console_lock ();console_srcu_write_flags (console, console->flags & ~CON_ENABLED ); -console_unlock ();console_list_unlock ();/*
@@ -3127,9 +3125,7 @@ EXPORT_SYMBOL(console_stop);void console_start (struct console *console) {console_list_lock (); -console_lock ();console_srcu_write_flags (console, console->flags |CON_ENABLED ); -console_unlock ();console_list_unlock ();__pr_flush (console,1000 , true); }
@@ -3246,6 +3242,12 @@ static void console_init_seq(struct console *newcon, bool bootcon_registered)* the furthest behind. */ if (bootcon_registered && !keep_bootcon) { +/* +* Hold the console_lock to stop console printing and +* guarantee safe access to console->seq. +*/ +console_lock (); +/* * Flush all consoles and set the console to start at * the next unprinted sequence number.
@@ -3272,6 +3274,8 @@ static void console_init_seq(struct console *newcon, bool bootcon_registered) } } } + +console_unlock (); } } }
@@ -3370,7 +3374,6 @@ void register_console(struct console *newcon) } newcon->dropped =0 ; -console_lock ();console_init_seq (newcon, bootcon_registered);/*
@@ -3390,7 +3393,6 @@ void register_console(struct console *newcon) }else {hlist_add_behind_rcu (&newcon->node, console_list.first); } -console_unlock ();/* * No need to synchronize SRCU here! The caller does not rely
@@ -3438,15 +3440,11 @@ static int unregister_console_locked(struct console *console)if (res >0 )return 0 ; -console_lock (); -/* Disable it unconditionally */ console_srcu_write_flags (console, console->flags & ~CON_ENABLED ); -if (!console_is_registered_locked (console)) { -console_unlock (); +if (!console_is_registered_locked (console))return -ENODEV ; - }hlist_del_init_rcu (&console->node);
@@ -3462,8 +3460,6 @@ static int unregister_console_locked(struct console *console)if (!hlist_empty (&console_list) && console->flags &CON_CONSDEV )console_srcu_write_flags (console_first (),console_first ()->flags |CON_CONSDEV ); -console_unlock (); -/* * Ensure that all SRCU list walks have completed. All contexts * must not be able to see this console in the list so that any
Signature · 1 line
2.30.2
Re: [PATCH printk v5 39/40] printk: relieve console_lock of list synchronization duties
Quoted 9 lines · John Ogness
The
console_list_lockprovides synchronization for console list andconsole->flagsupdates. All call sites that were using theconsole_lockfor this synchronization have either switched to use theconsole_list_lockor the SRCU list iterator.Remove
console_lockusage for console list updates andconsole->flagsupdates.Signed-off-by John Ogness <[email protected]>
Best Regards,
Petr
John Ogness
maintainerPATCH v5 40/40 tty: serial: sh-sci: use setup() callback for early console
In reply to John OgnessWhen setting up the early console, the setup() callback of the regular console is used. It is called manually before registering the early console instead of providing a setup() callback for the early console. This is probably because the early setup needs a different @options during the early stage.
The issue here is that the setup() callback is called without the console_list_lock held and functions such as uart_set_options() expect that.
Rather than manually calling the setup() function before registering, provide an early console setup() callback that will use the different early options. This ensures that the error checking, ordering, and locking context when setting up the early console are correct.
Since this early console can only be registered via the earlyprintk= parameter, the @options argument of the setup() callback will always be NULL. Rather than simply ignoring the argument, add a WARN_ON() to get our attention in case the setup() callback semantics should change in the future.
Note that technically the current implementation works because it is only used in early boot. And since the early console setup is performed before registering, it cannot race with anything and thus does not need any locking. However, longterm maintenance is easier when drivers rely on the subsystem API rather than manually implementing steps that could cause breakage in the future.
--- drivers/tty/serial/sh-sci.c | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-)
drivers/tty/serial/sh-sci.c +16 -4
@@ -3054,15 +3054,29 @@ static struct console serial_console = { };#ifdef CONFIG_SUPERH +static char early_serial_buf[32 ]; + +static int early_serial_console_setup (struct console *co,char *options) +{ +/* +* This early console is always registered using the earlyprintk= +* parameter, which does not call add_preferred_console(). Thus +* @options is always NULL and the options for this early console +* are passed using a custom buffer. +*/ +WARN_ON (options); + +return serial_console_setup (co, early_serial_buf); +} +static struct console early_serial_console = { .name ="early_ttySC" , .write = serial_console_write, + .setup = early_serial_console_setup, .flags =CON_PRINTBUFFER , .index =-1 , }; -static char early_serial_buf[32 ]; -static int sci_probe_earlyprintk (struct platform_device *pdev) {const struct plat_sci_port *cfg =dev_get_platdata (&pdev->dev);
@@ -3074,8 +3088,6 @@ static int sci_probe_earlyprintk(struct platform_device *pdev)sci_init_single (pdev, &sci_ports[pdev->id], pdev->id, cfg, true); -serial_console_setup (&early_serial_console, early_serial_buf); -if (!strstr (early_serial_buf,"keep" )) early_serial_console.flags |=CON_BOOT ;
Signature · 1 line
2.30.2
Petr Mladek
maintainerQuoted 6 lines · John Ogness
This is v5 of a series to prepare for threaded/atomic printing. v4 is here [0]. This series focuses on reducing the scope of the BKL
console_lock. It achieves this by switching to SRCU and a dedicated mutex for console list iteration and modification, respectively. Theconsole_lockwill no longer offer this protection.
The patchset looks ready for linux-next from my POV.
I am going to push it there right now to get as much testing as possible before the merge window.
Any review and comments are still appreciate. We could always take it back if some critical problems are discovered and can't be solved easily.
Best Regards,
Petr
Petr Mladek
maintainerQuoted 8 lines · Petr Mladek
Quoted 6 lines · John Ogness
This is v5 of a series to prepare for threaded/atomic printing. v4 is here [0]. This series focuses on reducing the scope of the BKL
console_lock. It achieves this by switching to SRCU and a dedicated mutex for console list iteration and modification, respectively. Theconsole_lockwill no longer offer this protection.
Quoted 4 lines
The patchset looks ready for linux-next from my POV.
I am going to push it there right now to get as much testing as possible before the merge window.
JFYI, the patchset is committed in printk/linux.git, branch rework/console-list-lock.
I'll eventually merge it into rework/kthreads. But I wanted to have it separated until it gets some more testing in linux-next and eventually some more review.
Best Regards,
Petr
Quoted 42 lines · John Ogness
This is v5 of a series to prepare for threaded/atomic printing. v4 is here [0]. This series focuses on reducing the scope of the BKL
console_lock. It achieves this by switching to SRCU and a dedicated mutex for console list iteration and modification, respectively. Theconsole_lockwill no longer offer this protection.Also, during the review of v2 it came to our attention that many console drivers are checking
CON_ENABLEDto see if they are registered. Because this flag can change without unregistering and because this flag does not represent an atomic point when an (un)registration process is complete, a newconsole_is_registered()function is introduced. This function uses theconsole_list_lockto synchronize with the (un)registration process to provide a reliable status.All users of the
console_lockfor list iteration have been modified. For the call sites where theconsole_lockis still needed (for other reasons), comments are added to explain exactly why theconsole_lockis needed.All users of
CON_ENABLEDfor registration status have been modified to useconsole_is_registered(). Note that there are still users ofCON_ENABLED, but this is for legitimate purposes about a registered console being able to print.The base commit for this series is from Paul McKenney's RCU tree and provides an NMI-safe SRCU implementation [1]. Without the NMI-safe SRCU implementation, this series is not less safe than mainline. But we will need the NMI-safe SRCU implementation for atomic consoles anyway, so we might as well get it in now. Especially since it _does_ increase the reliability for mainline in the panic path.
Changes since v4:
printk:
- Introduce
console_init_seq()to handle the now rather complex procedure to find an appropriate start sequence number for a new console upon registration.
Quoted 8 lines
- When registering a non-boot console and boot consoles are registered, try to flush all the consoles to get the next @seq value before falling back to use the @seq of the enabled boot console that is furthest behind.
- For
console_force_preferred_locked(), make the console the head of the console list.
_______________________________________________
linux-um mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-um