Re: [PATCH 08/13] securityselinuxhelper: Use g_new0() instead of malloc()+memset() combo

2023-08-03 Thread Michal Prívozník
On 8/3/23 13:29, Claudio Fontana wrote: > On 8/3/23 12:36, Michal Privoznik wrote: >> Inside of securityselinuxhelper we still use malloc() + >> memset(.., 0, ...) combo. Convert it to g_new0(). >> >> Signed-off-by: Michal Privoznik > > I don't think it is a good idea to mix Glib g_new, g_free

Re: [PATCH 08/13] securityselinuxhelper: Use g_new0() instead of malloc()+memset() combo

2023-08-03 Thread Claudio Fontana
On 8/3/23 12:36, Michal Privoznik wrote: > Inside of securityselinuxhelper we still use malloc() + > memset(.., 0, ...) combo. Convert it to g_new0(). > > Signed-off-by: Michal Privoznik I don't think it is a good idea to mix Glib g_new, g_free etc with malloc, calloc, free. If you go with

[PATCH 08/13] securityselinuxhelper: Use g_new0() instead of malloc()+memset() combo

2023-08-03 Thread Michal Privoznik
Inside of securityselinuxhelper we still use malloc() + memset(.., 0, ...) combo. Convert it to g_new0(). Signed-off-by: Michal Privoznik --- tests/securityselinuxhelper.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/tests/securityselinuxhelper.c