linux-kernel - smatch_scripts/whitespace

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]

Date:	Wed, 10 Mar 2010 13:12:24 +0300
From:	Dan Carpenter <error27@...il.com>
To:	linux-kernel@...r.kernel.org, gregkh@...e.de,
	kernel-janitors@...r.kernel.org, devel@...verdev.osuosl.org
Subject: smatch_scripts/whitespace_only.sh

I wrote a script to check that a patch only changes white space.
It compiles the files before and after the patch is applied and 
verifies that they are the same.

You'll need to compile smatch:
	git pull git://repo.or.cz/smatch.git
	make
	cd /path/to/kernel/src/
	/path/to/smatch_scripts/whitespace_only.sh <patch>

Adding or removing parenthesis and curly braces counts as a code 
change.  Changes to comments, #if 0, white space changes do not.

You can fix a lot of style violations if you limit yourself to 
adding and removing tabs, spaces and new lines.  Then the next 
patch could remove unneeded parenthesis.  It would be easier to
audit that way instead of everything mixed together.

regards,
dan carpenter

PS.  I feel really bad slagging the newbies trying to help.  
Could we fix checkpatch.pl to not complain about line lengths?
Also could we tell them to stay in staging where no one cares
about git blame?

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