* jianchunfu ([email protected]) wrote: > Using macro g_new() to handling potential memory allocation failures > in dirtyrate. > > Signed-off-by: jianchunfu <[email protected]> > --- > migration/dirtyrate.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/migration/dirtyrate.c b/migration/dirtyrate.c > index aace12a787..0e59aacbb0 100644 > --- a/migration/dirtyrate.c > +++ b/migration/dirtyrate.c > @@ -522,10 +522,10 @@ static void calculate_dirtyrate_dirty_ring(struct > DirtyRateConfig config) > nvcpu++; > } > > - dirty_pages = malloc(sizeof(*dirty_pages) * nvcpu); > + dirty_pages = g_new(DirtyPageRecord, nvcpu); > > DirtyStat.dirty_ring.nvcpu = nvcpu; > - DirtyStat.dirty_ring.rates = malloc(sizeof(DirtyRateVcpu) * nvcpu); > + DirtyStat.dirty_ring.rates = g_new(DirtyRateVcpu, nvcpu); > > dirtyrate_global_dirty_log_start();
Reviewed-by: Dr. David Alan Gilbert <[email protected]> > > -- > 2.18.4 > > > -- Dr. David Alan Gilbert / [email protected] / Manchester, UK
