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>] [day] [month] [year] [list]
Message-ID: <20150703164944.GG9456@thunk.org>
Date:	Fri, 3 Jul 2015 12:49:44 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	nick <xerofoify@...il.com>
Cc:	Michal Hocko <mhocko@...e.cz>, akpm@...ux-foundation.org,
	mgorman@...e.de, n-horiguchi@...jp.nec.com, sasha.levin@...cle.com,
	Yalin.Wang@...ymobile.com, jmarchan@...hat.com,
	kirill@...temov.name, rientjes@...gle.com, vbabka@...e.cz,
	aneesh.kumar@...ux.vnet.ibm.com, ebru.akagunduz@...il.com,
	hannes@...xchg.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH] mm:Make the function zap_huge_pmd bool

On Fri, Jul 03, 2015 at 11:03:11AM -0400, nick wrote:
> 
> The reason I am doing this is Ted is trying to find a bug that I
> fixed in order to prove to Greg Kroah Hartman I have
> changed. Otherwise I would be pushing this through the drm
> maintainer(s).

I am trying to determine if you have changed.  Your comment justifying
your lack of testing because "it's hard to test" is ample evidence
that you have *not* changed.

Simply coming up with a commit that happens to be correct is a
necessary, but not sufficient condition.  Especially when you feel
that you need to send dozens of low-value patches and hope that one of
them is correct, and then use that as "proof".  It's the attitude
which is problem, not whether or not you can manage to come up with a
correct patch.

I've described to you what you need to do in order to demonstrate that
you have the attitude and inclinations in order to be a kernel
developer that a maintainer can trust as being capable of authoring a
patch that doesn't create more problems than whatever benefits it
might have.  I respectfully ask that you try to work on that, and stop
bothering me (and everyone else).

Best regards,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ