linux/Documentation/admin-guide/kdump
John Ogness dd4f59bb3b 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>
History 2023-03-10 09:29:49 +01:00
..
gdbmacros.txt docs: gdbmacros: print newest record 2023-03-10 09:29:49 +01:00
index.rst docs: admin-guide: add kdump documentation into it 2019-07-15 11:03:01 -03:00
kdump.rst docs: kdump: add scp example to write out the dump file 2022-03-23 19:00:34 -07:00
vmcoreinfo.rst Documentation: kdump: describe VMCOREINFO export for RISCV64 2022-12-02 16:48:58 -08:00