linux-kernel - [PATCH 0/2] x86: use stdout for success and stdout for failure

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: <1477428965-20548-1-git-send-email-pebolle@tiscali.nl>
Date:   Tue, 25 Oct 2016 22:56:03 +0200
From:   Paul Bolle <pebolle@...cali.nl>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] x86: use stdout for success and stdout for failure

For some time now my x86 builds are warning free. Yay! But there's still one
single line printed to stderr:
    Succeed: decoded and checked 1767380 instructions

This message is printed if the "insn decoder test" ran successful. Patch 1/2
sends this message to stdout (and fixes the typo).

Patch 2/2 does the reverse for the "insn sanity test": it sends a message to
stderr if that test fails.

One thing puzzles me about these two tests: I must have run them hundreds of
times but I've never seen them fail. Have other people ran into failures?

Paul Bolle (2):
  x86: use stdout if insn decoder test is successful
  x86: use stderr if insn sanity test fails

 arch/x86/tools/insn_sanity.c  | 3 ++-
 arch/x86/tools/test_get_len.c | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

-- 
2.7.4