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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <878t56rpc9.fsf@jidanni.org>
Date:   Fri, 17 Aug 2018 05:09:10 +0800
From:   Dan Jacobson <jidanni@...anni.org>
To:     linux-kernel@...r.kernel.org
Subject: Say what the -[ cut here ]- lines are called

The kernel should really say what the
------------[ cut here ]------------
lines are called, else users will say things like:

"I discovered that the user needs to use xrandr in _two_ steps for
certain resolutions, else he will trigger a
kernel:  ------------[ cut here ]------------ line."

instead of
"...will trigger a kernel problem."
"...will trigger a kernel fault."
"...will trigger a kernel oops."
or whatever it is supposed to be called.

So say e.g.,
------------[ cut here ]------------
Kernel fault:

etc. there in the syslog. Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ