linux-kernel - Re: [PATCH 00/24] drivers/block/floppy.c cleanups

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: <20100122090441.10716815@nehalam>
Date:	Fri, 22 Jan 2010 09:04:41 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Andi Kleen <andi@...stfloor.org>, Joe Perches <joe@...ches.com>,
	linux-kernel@...r.kernel.org,
	Marcin Slusarz <marcin.slusarz@...il.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 00/24] drivers/block/floppy.c cleanups

On Fri, 22 Jan 2010 11:46:53 +0000
Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > Philosophically I'm not sure it's that great an idea to make bad code
> > look better without actually fixing/rewriting it. It's like putting
> > lipstick on a pig.
> 
> Unpacking the mess and sorting out the whacky macros is more like
> removing all muck from the mechanism so you can see what needs to be done.
> 
> So I disagree - its a useful first step only

I had a reason in motivating this. For some cases, customers use floppy as
a configuration storage, and there were a number of strange errors
showing up occasionally in recent kernels. But the driver is such
an old crufty mess, it wasn't worth investigating further.

Making the code clearer gets rid of that excuse.

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