linux-kernel - Re: [PATCH] MIPS: kernel: proc: Remove spurious white space in cpuinfo

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

Message-ID: <alpine.DEB.2.00.1710202129250.3886@tp.orcam.me.uk>
Date:   Fri, 20 Oct 2017 21:47:51 +0100
From:   "Maciej W. Rozycki" <macro@...s.com>
To:     Aleksandar Markovic <aleksandar.markovic@...rk.com>
CC:     <linux-mips@...ux-mips.org>,
        Dragan Cecavac <dragan.cecavac@...s.com>,
        Aleksandar Markovic <aleksandar.markovic@...s.com>,
        Douglas Leung <douglas.leung@...s.com>,
        Goran Ferenc <goran.ferenc@...s.com>,
        James Hogan <james.hogan@...s.com>,
        James Hogan <jhogan@...nel.org>,
        <linux-kernel@...r.kernel.org>,
        "Maciej W. Rozycki" <macro@...ux-mips.org>,
        Miodrag Dinic <miodrag.dinic@...s.com>,
        Paul Burton <paul.burton@...tec.com>,
        Paul Burton <paul.burton@...s.com>,
        Petar Jovanovic <petar.jovanovic@...s.com>,
        Raghu Gandham <raghu.gandham@...s.com>,
        "Ralf Baechle" <ralf@...ux-mips.org>
Subject: Re: [PATCH] MIPS: kernel: proc: Remove spurious white space in
 cpuinfo

On Fri, 20 Oct 2017, Aleksandar Markovic wrote:

> Remove unnecessary space from FPU info segment of /proc/cpuinfo.

 NAK.  As I recall back in Nov 2001 I placed the extra space there to 
visually separate the CPU part from the FPU part, e.g.:

cpu model		: R3000A V3.0  FPU V4.0
cpu model		: SiByte SB1 V0.2  FPU V0.2

etc.  And the motivation behind it still stands.  Please remember that 
/proc/cpuinfo is there for live humans to parse and grouping all these 
pieces together would make it harder.  Which means your change adds no 
value I'm afraid.

 NB regrettably back in those days much of the patch traffic happened off 
any mailing list, however I have quickly tracked down my archival copy of 
the original submission of the change introducing this piece of code and
I'll be happy to share it with anyone upon request.

  Maciej