linux-kernel - Re: [tip:timers/core] timekeeping: Increase granularity of read_persistent

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: <1251279864.1379.62.camel@pasglop>
Date:	Wed, 26 Aug 2009 19:44:23 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Paul Mackerras <paulus@...ba.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	dwalker@...o99.com, mingo@...hat.com, hpa@...or.com,
	linux-kernel@...r.kernel.org, johnstul@...ibm.com,
	tglx@...utronix.de, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:timers/core] timekeeping: Increase granularity of
 read_persistent_clock()

On Tue, 2009-08-25 at 15:50 +0200, Ingo Molnar wrote:
> 
> Well, me pointing out that such measures slow down the critical path 
> of patch submission is a valid concern - and "you are not forced to 
> do that" pretty much defeats you having suggested it, doesnt it? (i 
> hope i'm not misprepresenting your words)
> 
My problem with you is precisely there.

"The critical path of patch submission"

You seem to consider it a holy objective to shove as much stuff into
Linux as can be produced and as fast as possible. Your previous comment
about not slowing down the process is in the similar vein.

That's something that I would hear out of a corporate executive, not a
Linux kernel hacker and especially not one who is a maintainer.

Changes at all cost is not a panacea, nor are we in some kind of "race"
to get the must stuff in as you can manage. We should take the time to
make sure things are done right, and if a patch has a problem, then fix
the patch and rebase before it hits upstream.

This is good and sane process, nothing else.

Cheers,
Ben.

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