Le 20/10/2020 à 09:36, Chenqun (kuhn) a écrit : > Ping! > > Hello, > > Maybe this patch, some people have any other suggestions? Or, maybe > missed to queue?
Hi, As we've seen by reviewing previous versions, this change is not really trivial, so I will not take it via the trivial queue. Perhaps via block I/O queue (Stefan?), Dirty Bitmaps (John?) or Migration (Juan?). Thanks, Laurent > Thanks, > Chen Qun > >> -----Original Message----- >> From: Vladimir Sementsov-Ogievskiy [mailto:[email protected]] >> Sent: Wednesday, October 14, 2020 11:56 PM >> To: Chenqun (kuhn) <[email protected]>; [email protected]; >> [email protected] >> Cc: [email protected]; [email protected]; [email protected]; >> [email protected]; [email protected]; [email protected]; >> [email protected]; Zhanghailiang <[email protected]>; >> ganqixin <[email protected]>; [email protected]; Euler Robot >> <[email protected]>; Laurent Vivier <[email protected]>; Li Qiang >> <[email protected]> >> Subject: Re: [PATCH v3] migration/block-dirty-bitmap: fix uninitialized >> variable >> warning >> >> 14.10.2020 14:44, Chen Qun wrote: >>> A default value is provided for the variable 'bitmap_name' to avoid compiler >> warning. >>> >>> The compiler show warning: >>> migration/block-dirty-bitmap.c:1090:13: warning: ‘bitmap_name’ >>> may be used uninitialized in this function [-Wmaybe-uninitialized] >>> g_strlcpy(s->bitmap_name, bitmap_name, >> sizeof(s->bitmap_name)); >>> >> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> >>> Reported-by: Euler Robot<[email protected]> >>> Signed-off-by: Chen Qun<[email protected]> >> >> Reviewed-by: Vladimir Sementsov-Ogievskiy <[email protected]> >> >> -- >> Best regards, >> Vladimir
