John Ogness f9f3f02db9 printk: introduce a kmsg_dump iterator ... Rather than storing the iterator information in the registered kmsg_dumper structure, create a separate iterator structure. The kmsg_dump_iter structure can reside on the stack of the caller, thus allowing lockless use of the kmsg_dump functions. Update code that accesses the kernel logs using the kmsg_dumper structure to use the new kmsg_dump_iter structure. For kmsg_dumpers, this also means adding a call to kmsg_dump_rewind() to initialize the iterator. All this is in preparation for removal of @logbuf_lock. Signed-off-by: John Ogness <john.ogness@linutronix.de> Reviewed-by: Kees Cook <keescook@chromium.org> # pstore Reviewed-by: Petr Mladek <pmladek@suse.com> Signed-off-by: Petr Mladek <pmladek@suse.com> Link: https://lore.kernel.org/r/20210303101528.29901-13-john.ogness@linutronix.de		2021-03-08 11:43:27 +01:00
..
kdb	printk: introduce a kmsg_dump iterator	2021-03-08 11:43:27 +01:00
debug_core.c	smp: Cleanup smp_call_function*()	2020-11-24 16:47:49 +01:00
debug_core.h	kdb: Fix stack crawling on 'running' CPUs that aren't the master	2019-10-10 16:28:48 +01:00
gdbstub.c	kernel: debug: Centralize dbg_[de]activate_sw_breakpoints	2020-10-01 14:23:45 +01:00
Makefile	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00