From: Avi Kivity <avi@redhat.com>
To: Alan Cox <alan@linux.intel.com>
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>
Subject: Re: + ppc-e500_tlb-memset-clears-nothing.patch added to -mm tree
Date: Wed, 25 Jul 2012 13:20:20 +0300 [thread overview]
Message-ID: <500FC864.8070705@redhat.com> (raw)
In-Reply-To: <20120725111218.1da93765@bob.linux.org.uk>
On 07/25/2012 01:12 PM, Alan Cox wrote:
>> 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.
It's pretty easy with BUILD_BUG_ON(), unfortunately that emits an error
and there may be legitimate uses for memset(p, 255, 0).
> Fortunately a lot of other validation/verification tools do pick it up
> already.
Also a lot of kernel developers whose time would be better spent on
other things.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-25 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 21:00 + ppc-e500_tlb-memset-clears-nothing.patch added to -mm tree akpm
2012-07-25 8:32 ` Avi Kivity
2012-07-25 9:00 ` Alexander Graf
2012-07-25 9:20 ` Avi Kivity
2012-07-25 10:12 ` Alan Cox
2012-07-25 10:20 ` Avi Kivity [this message]
2012-07-25 10:10 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=500FC864.8070705@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=dcb314@hotmail.com \
--cc=kvm@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.