linux-kernel - Re: [PATCH] x86, UV: Reformat uv_mmrs.h

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]

Date:	Fri, 13 May 2011 14:40:29 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jack Steiner <steiner@....com>
Cc:	tglx@...utronix.de, hpa@...or.com, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86, UV: Reformat uv_mmrs.h - no code changes

* Jack Steiner <steiner@....com> wrote:

> No code changes.  Reformat file to eliminate errors caught
> by checkpatch.pl
> 
> Signed-off-by: Jack Steiner <steiner@....com>
> 
> ---
>  arch/x86/include/asm/uv/uv_mmrs.h | 1147 ++++++++++++++++++--------------------
>  1 file changed, 573 insertions(+), 574 deletions(-)

Firstly, the patch does not apply to -tip cleanly.

Secondly, and more importantly, you are only addressing checkpatch errors but 
you are not looking at the end result! The goal is to make the code nicer to 
look at.

 Good example: uvh_event_occurred0_u, uvh_lb_bau_intd_software_acknowledge_u
  Bad example: uvh_bau_data_config_u and most of the other definitions!

There's a couple of other problems as well.

Why the heck is this symbol:

  #define UVH_LB_BAU_MISC_CONTROL_INTD_SOFT_ACK_TIMEOUT_PERIOD_SHFT 16

56 characters long?! Was there possibly no way to make it even longer?

And of course, once used, this symbol craps up the code in 
arch/x86/platform/uv/tlb_uv.c ...

Using BAU_MISC_ACK_PERIOD_SHIFT would be like 3 times shorter, and still as 
obvious. Or if these are the result of some Verilog tooling dependency then 
please keep these tucked away in the .h and use some sensible symbol instead, 
never pollute the .c file with the insanely long symbol names!

Also, if you look at the line of definitions you will see the same kind of 
ugliness you can see at uvh_bau_data_config_u et al.

And then i have not even started about enable_programmed_initial_priority 
structure fields.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/