qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: jcd@tribudubois.net
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] use qemu_malloc and friends consistently
Date: Fri, 29 May 2009 10:28:03 +0100 (GMT+01:00)	[thread overview]
Message-ID: <20380459.68691243589283394.JavaMail.root@srv-05.w4a.fr> (raw)
In-Reply-To: <4A1F9FFE.3030100@redhat.com>

Hi Kevin,

Thanks for pointing this. I guess it just sounds strange to me that somebody would want to alloc 0 bytes. But why not ...

I guess that if pattern_count/count is set to 0 we can just avoid the all processing of malloc/memset/memcmp/free anyway.

Would you be ok with something like:

if (Pflag && pattern_count) {

instead of: 

if (Pflag) {

JC

----- Mail Original -----
De: "Kevin Wolf" <kwolf@redhat.com>
À: "Jean-Christophe Dubois" <jcd@tribudubois.net>
Cc: qemu-devel@nongnu.org, "malc" <av1474@comtv.ru>
Envoyé: Vendredi 29 Mai 2009 10h42:38 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [Qemu-devel] [PATCH] use qemu_malloc and friends consistently

Jean-Christophe Dubois schrieb:
> qemu_malloc, qemu_free and friends are not used consistently in the qemu 
> source code.
> 
> This is a first attempt to use these oveloaded functions consistently all over 
> the place instead of the default glibc versions.
> 
> Signed-off-by: Jean-Christophe DUBOIS <jcd@tribudubois.net>

[...]

> diff -rNu qemu.org/qemu-io.c qemu/qemu-io.c
> --- qemu.org/qemu-io.c	2009-05-16 17:57:27.000000000 +0200
> +++ qemu/qemu-io.c	2009-05-18 23:48:23.000000000 +0200
> @@ -311,14 +311,14 @@
>  	}
>  
>  	if (Pflag) {
> -		void* cmp_buf = malloc(pattern_count);
> +		void* cmp_buf = qemu_malloc(pattern_count);
>  		memset(cmp_buf, pattern, pattern_count);
>  		if (memcmp(buf + pattern_offset, cmp_buf, pattern_count)) {
>  			printf("Pattern verification failed at offset %lld, "
>  				"%d bytes\n",
>  				(long long) offset + pattern_offset, pattern_count);
>  		}
> -		free(cmp_buf);
> +		qemu_free(cmp_buf);
>  	}
>  
>  	if (qflag)
> @@ -465,14 +465,14 @@
>  	}
>  
>  	if (Pflag) {
> -		void* cmp_buf = malloc(count);
> +		void* cmp_buf = qemu_malloc(count);
>  		memset(cmp_buf, pattern, count);
>  		if (memcmp(buf, cmp_buf, count)) {
>  			printf("Pattern verification failed at offset %lld, "
>  				"%d bytes\n",
>  				(long long) offset, count);
>  		}
> -		free(cmp_buf);
> +		qemu_free(cmp_buf);
>  	}
>  
>  	if (qflag)

Since recently qemu_malloc behaves differently from malloc with size =
0. This isn't allowed any more with qemu_malloc. So you need to check
for pattern_count == 0 and either print an error message or malloc a
different size, e.g. 1. I'm sure we don't want qemu-io to abort() in
such a case.

Or we could start over with a lengthy discussion about fixing qemu_malloc...

Kevin

  parent reply	other threads:[~2009-05-29  9:28 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  5:58 [Qemu-devel] [PATCH] use qemu_malloc and friends consistently Jean-Christophe Dubois
2009-05-29  8:42 ` Kevin Wolf
2009-05-29  9:05   ` Anthony Liguori
2009-05-29  9:51     ` malc
2009-05-29 10:05       ` Kevin Wolf
2009-05-29 10:23         ` malc
2009-05-29 10:34           ` Kevin Wolf
2009-05-29 10:40             ` malc
2009-05-29 10:49               ` Kevin Wolf
2009-05-29 10:56                 ` Anthony Liguori
2009-05-29 11:06                 ` malc
2009-05-29 11:14                   ` Kevin Wolf
2009-05-29 10:53       ` Anthony Liguori
2009-05-29 11:24         ` malc
2009-05-29 12:36           ` Gerd Hoffmann
2009-05-29 13:07             ` Paul Brook
2009-05-29 13:46               ` Gerd Hoffmann
2009-05-29 13:59               ` Glauber Costa
2009-05-29 14:34               ` Anthony Liguori
2009-05-29 15:06                 ` malc
2009-05-29 17:17               ` Julian Seward
2009-05-29 18:41                 ` Gerd Hoffmann
2009-05-29 21:12                 ` David Turner
2009-05-29 21:13                   ` David Turner
2009-06-02  7:26                   ` Gerd Hoffmann
2009-06-02  7:47                     ` Anthony Liguori
2009-06-02  8:58                       ` Daniel P. Berrange
2009-06-02 18:03                         ` David Turner
2009-06-02  8:48                     ` Avi Kivity
2009-06-02 18:02                     ` David Turner
2009-06-02 18:13                       ` Paul Brook
2009-06-02 19:49                         ` David Turner
2009-06-02 20:04                           ` Paul Brook
2009-06-02 20:42                             ` David Turner
2009-06-02 20:45                               ` Gerd Hoffmann
2009-06-02 20:48                               ` Gerd Hoffmann
2009-06-02 20:58                               ` Paul Brook
2009-06-02 21:19                                 ` David Turner
2009-06-02 19:03                       ` Avi Kivity
2009-05-29 12:51           ` Markus Armbruster
2009-05-29 10:57       ` Gerd Hoffmann
2009-05-29 11:28         ` malc
2009-05-29  9:28   ` jcd [this message]
2009-05-29  9:38     ` Kevin Wolf
2009-06-01 11:59     ` Jamie Lokier
     [not found] <18212122.68761243590277678.JavaMail.root@srv-05.w4a.fr>
2009-05-29 10:00 ` jcd
2009-05-29 10:10   ` Kevin Wolf
     [not found] <2171027.69001243598252547.JavaMail.root@srv-05.w4a.fr>
2009-05-29 12:00 ` jcd
2009-05-29 12:05   ` Kevin Wolf
2009-05-29 12:13     ` jcd
2009-05-29 12:32   ` Markus Armbruster
2009-05-29 12:38     ` jcd
     [not found] <28932640.69341243603994530.JavaMail.root@srv-05.w4a.fr>
2009-05-29 13:35 ` jcd
     [not found] <28912134.69441243608238156.JavaMail.root@srv-05.w4a.fr>
2009-05-29 14:46 ` jcd
     [not found] <33383337.69831243610071896.JavaMail.root@srv-05.w4a.fr>
2009-05-29 15:15 ` jcd
     [not found] <1758936.71791243858884274.JavaMail.root@srv-05.w4a.fr>
2009-06-01 12:24 ` jcd
2009-06-01 23:46   ` Jamie Lokier

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=20380459.68691243589283394.JavaMail.root@srv-05.w4a.fr \
    --to=jcd@tribudubois.net \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).