linux-stable/Documentation/admin-guide/kdump
John Ogness d0d794371b docs: gdbmacros: print newest record
commit f2e4cca2f6 upstream.

@head_id points to the newest record, but the printing loop
exits when it increments to this value (before printing).

Exit the printing loop after the newest record has been printed.

The python-based function in scripts/gdb/linux/dmesg.py already
does this correctly.

Fixes: e60768311a ("scripts/gdb: update for lockless printk ringbuffer")
Cc: stable@vger.kernel.org
Signed-off-by: John Ogness <john.ogness@linutronix.de>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20221229134339.197627-1-john.ogness@linutronix.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2023-03-10 09:40:09 +01:00
..
gdbmacros.txt docs: gdbmacros: print newest record 2023-03-10 09:40:09 +01:00
index.rst
kdump.rst Documentation: kdump: update kdump guide 2021-06-14 08:12:01 -06:00
vmcoreinfo.rst kdump: append uts_namespace.name offset to VMCOREINFO 2020-12-15 22:46:18 -08:00