linux-kernel - Re: [PATCH] vt: add an event interface

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: <20090703114431.37abd528@lxorguk.ukuu.org.uk>
Date:	Fri, 3 Jul 2009 11:44:31 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] vt: add an event interface

> > Which is a cut and paste of code from the originals into the 
> > helper.
> 
> and this changes my points how? It's not like it's hard to fix, and 
> the code is moved non-trivially anyway, it's better to have it nicer 
> if we touch it anyway.

Its called engineering and good practice. The old code was correct. The
paste of it is therefore most likely to be correct. Furthermore patches
shouldn't mix clean up with other changes. So doing it as one is most
definitely bad practice.

> > > Also note the inconsistent printk-ing lines, mutiliated by line 
> > > warps. The use of pr_warning() would solve it:
> > 
> > Send patches if it bugs you that much. [...]
> 
> I find that a rather flippant attitude to kernel code quality 
> issues.

I have better uses for my time than fiddling with pr_warning(). Fixing
real bugs for example, bugs that crash your system, broken locking that
goes back to Linux 2.2 and DaveM's original push of lock_kernel out of
IRQ paths

> Also, isnt it a double standard: why should newbies be held to 
> higher standards than you hold yourself to?

Why should anyone be held up to bogus standards ?

To bend an appropriate metaphor Ingo - you are trying to criticize the
paint finish of the bike shed while some of us are still replacing the
rusted and corroded beams.

If it was a new bike shed you might be in order, but at the moment the
tty layer is rescue archaeology and I'm spending my time doing useful
things like fixing the real bugs and getting from where we are now to
somewhere useful without causing too much carnage on the way. pr_warning
is an end of the journey polishing job.

The x86 experience doesn't translate here - Andi left you a well
maintained, well polished starting point. Nobody has been maintaining tty
for years.

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