Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+libipvs\:\s+Initialize\s+ipvs_service_t\s+variable\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH] libipvs: Initialize ipvs_service_t variable (score: 1)
Author: Jesper Dangaard Brouer <jbrouer@xxxxxxxxxx>
Date: Thu, 6 Mar 2014 11:05:24 +0100
Thanks Ryan, Applied the patch. More followup patches to address more areas are welcome. Git tree for ipvsadm avail at: https://git.kernel.org/cgit/utils/kernel/ipvsadm/ipvsadm.git/ -- Best regards,
/html/lvs-devel/2014-03/msg00000.html (10,918 bytes)

2. Re: [PATCH] libipvs: Initialize ipvs_service_t variable (score: 1)
Author: "Ryan O'Hara" <rohara@xxxxxxxxxx>
Date: Fri, 17 Jan 2014 15:15:17 -0600
Right. This 'bug' was found while running the code through a static analyzer, which finds all sorts of nit-picks. Since the variable in question here is on the stack, a simple memset seems sufficient
/html/lvs-devel/2014-01/msg00004.html (10,700 bytes)

3. Re: [PATCH] libipvs: Initialize ipvs_service_t variable (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Fri, 17 Jan 2014 23:03:43 +0200 (EET)
Hello, Yes, it is a good idea. Another variant is to change malloc to calloc. May be ipvs_nl_fill_service_attr() can not crash in all cases when reading svc->pe_name[]. As for the kernel part, ip_vs_
/html/lvs-devel/2014-01/msg00003.html (10,446 bytes)

4. [PATCH] libipvs: Initialize ipvs_service_t variable (score: 1)
Author: "Ryan O'Hara" <rohara@xxxxxxxxxx>
Date: Fri, 17 Jan 2014 11:53:46 -0600
The ipvs_get_service function declares an ipvs_service_t type variable and initializes some of the values, but should really start by initializing the entire structure. Signed-off-by: Ryan O'Hara <ro
/html/lvs-devel/2014-01/msg00002.html (8,927 bytes)


This search system is powered by Namazu