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  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]
Date:   Thu, 12 Jul 2018 11:46:25 +0300
From:   Kirill Tkhai <>
Subject: [PATCH] bug-hunting.rst: Clarify bytes sequence format when making
 "Code:" human-readable

Bytes have to be separated commas, and this is not obvious
for a person, who does not write in pure ".byte" assembler.
Let's clarify this and make visible for people.

Signed-off-by: Kirill Tkhai <>
 Documentation/admin-guide/bug-hunting.rst |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/admin-guide/bug-hunting.rst b/Documentation/admin-guide/bug-hunting.rst
index f278b289e260..861ee752eae9 100644
--- a/Documentation/admin-guide/bug-hunting.rst
+++ b/Documentation/admin-guide/bug-hunting.rst
@@ -213,7 +213,7 @@ If you don't have access to the code you can also debug on some crash dumps
             .globl foo
-            .byte  .... /* bytes from Code: part of OOPS dump */
+            .byte  0x44,0x24,0x04,... /* bytes from Code: part of OOPS dump */
      Compile it with "gcc -c -o foo.o foo.s" then look at the output of
      "objdump --disassemble foo.o".

Powered by blists - more mailing lists