linux-kernel - Re: [Cluster-devel] Re: [GFS2] Change argument of gfs2_dinode

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: <20061201210849.GF3078@ftp.linux.org.uk>
Date:	Fri, 1 Dec 2006 21:08:49 +0000
From:	Al Viro <viro@....linux.org.uk>
To:	Russell Cattelan <cattelan@...barn.com>
Cc:	cluster-devel@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [Cluster-devel] Re: [GFS2] Change argument of gfs2_dinode_out [17/70]

On Fri, Dec 01, 2006 at 02:52:11PM -0600, Russell Cattelan wrote:
> code clean up are not without risk and with no regression test suite to
> verify
> that a "cleanup" has not broken something. Cleanups are very much a
> hindrance to stabilization. With no know working points in a code
> history it becomes difficult
> to bisect changes and figure out when bugs were introduced
> Especially when cleanups are mixed in with bug fixes.
> 
> Pretty code does not equal correct code.

No, but convoluted and unreadable code ends up being crappier due
to lack of review.  And that's aside of the memory footprint,
likeliness of bugs introduced by code modifications (having in-core
and on-disk data structures with different contents and the same C
type => trouble that won't be caught by compiler), etc.
-
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/