From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alan Cox <alan@linux.intel.com>
Subject: Re: + ppc-e500_tlb-memset-clears-nothing.patch added to -mm tree
Date: Wed, 25 Jul 2012 11:12:18 +0100
Message-ID: <20120725111218.1da93765@bob.linux.org.uk>
References: <20120724210054.4164420004E@hpza10.eem.corp.google.com>
	<500FAF05.8010304@redhat.com>
	<A8F92187-840B-4572-8952-7CD53227C362@suse.de>
	<500FBA69.9070402@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Alexander Graf <agraf@suse.de>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
	"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
	"dcb314@hotmail.com" <dcb314@hotmail.com>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	"paulus@samba.org" <paulus@samba.org>,
	KVM list <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mga01.intel.com ([192.55.52.88]:10578 "EHLO mga01.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751729Ab2GYJzL (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 25 Jul 2012 05:55:11 -0400
In-Reply-To: <500FBA69.9070402@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

> I wonder how many such bugs a memzero()/bzero() will prevent.

If the compiler-foo is possible with gcc then a 0 length constant
memset warning and a warning if the set value is > 255 would both
probably be useful.

Fortunately a lot of other validation/verification tools do pick it up
already.

Alan