linux-kernel - Re: [PATCH] mm:Make the function zap_huge

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-next>] [day] [month] [year] [list]

Message-ID: <20150703184501.GJ9456@thunk.org>
Date:	Fri, 3 Jul 2015 14:45:02 -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 12:52:06PM -0400, nick wrote:
> I agree with you 100 percent. The reason I can't test this is I don't have the
> hardware otherwise I would have tested it by now.

Then don't send the patch out.  Work on some other piece of part of
the kernel, or better yet, some other userspace code where testing is
easier.  It's really quite simple.

You don't have the technical skills, or at this point, the reputation,
to send patches without tesitng them first.  The fact that sometimes
people like Linus will send out a patch labelled with "COMPLETELY
UNTESTED", is because he's skilled and trusted enough that he can get
away with it.  You have neither of those advantages.

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/