linux-kernel - [RFC] Cleaning oopses

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>] [day] [month] [year] [list]

Date:   Wed, 7 Dec 2016 09:51:50 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     x86-ml <x86@...nel.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Peter Zijlstra <peterz@...radead.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: [RFC] Cleaning oopses

Hi guys,

should we add a simple script like below to scripts/ or so to use for
cleaning up oopses before adding to commit messages?

Instead of doing all the work by hand and so on. It doesn't remove
registers, stack and Code: lines yet but having it in the repo could be
used to state exactly which pieces of the oops should go into a commit
message and which not.

We could even do editing on the oops itself for more readability and so
on...

Thoughts?

---
#!/bin/sh

sed --regexp-extended \
	    -e 's/\[\s+[0-9]+\.[0-9]+\]//' \
	    -e 's/\+[0-9x]+.*$//' \
	    -e 's/\[<.*>\]//' \
	    < "${1:-/dev/stdin}"

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.