linux-kernel - Re: [GIT PULL] x86/build change for v3.6

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

Message-ID: <20120729204240.GA26530@merkur.ravnborg.org>
Date:	Sun, 29 Jul 2012 22:42:40 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"Kirill A. Shutemov" <kirill@...temov.name>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] x86/build change for v3.6

On Thu, Jul 26, 2012 at 08:55:06AM +0200, Ingo Molnar wrote:
> 
> * Sam Ravnborg <sam@...nborg.org> wrote:
> 
> > > 
> > > No, the reason for the odd looking diff is that lots of lines in 
> > > arch/x86/Makefile have 8-space tabs for histerical reasons but 
> > > new code (such as this one) has proper tabs.
> > 
> > Use of tabs for indent in a Makefile is just asking for 
> > trouble.
> 
> Ok, I guess you are right - see the patch below which was 
> another type of bug that could be introduced via not using 
> spaces properly.
> 
> We could do it the other way around: turn all tabs into spaces 
> and add Makefile checking in kbuild so that the build fails if
> a tab is added to a Makefile?
> 
> Alternatively, is there perhaps some way to teach make to not be 
> so broken to depend on whitespace details that are *invisible* 
> to humans?
We can teach make to use something else - say "€" - as the command idicator.
But that would confuse people a lot.

If we follow hpa's suggestion to use 4 spaces as indent then it
more obvious that we do not use tabs for indent.
For that matter we could consider 3 spaces - so two indents is not
the same as one tab.

If we one day use a tool for parsing up all the kbuild files
then we could always add checks in that tool.
but today make does not allow us to do so.

At least not that I know.

	Sam
--
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/