linux-kernel - [RFC] printk's sync mode for ftrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211029102603.4qp4g5bzuydrbkrx@linutronix.de>
Date:   Fri, 29 Oct 2021 12:26:03 +0200
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     John Ogness <john.ogness@...utronix.de>,
        linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: [RFC] printk's sync mode for ftrace_dump()

ftrace_dump() is used for instance by alt-sysrq-z / sysrq_ftrace_dump().
The function itself dumps the whole trace buffer in an irq-off section so
no need to talk about max latencies unless this is going to change.

The output on the serial is more or less brief and starts with
    "** 397774 printk messages dropped **"
and so I do see only the end of it. Might be okay.
Any reason not to use the sync mode + atomic console while ftrace_dump()
is in progress?

Sebastian