From mboxrd@z Thu Jan 1 00:00:00 1970 From: bill.c.roberts@gmail.com (William Roberts) Date: Wed, 4 Oct 2017 11:05:46 -0700 Subject: [refpolicy] [PATCH v5] fc_sort: memory leakages In-Reply-To: <8861CE28-A39E-4779-8322-F59D251F6528@trentalancia.com> References: <1506643940.32317.6.camel@trentalancia.com> <1506703966.24492.1.camel@trentalancia.com> <1506710145.25223.1.camel@trentalancia.com> <1506727850.25420.6.camel@trentalancia.com> <1506751423.18819.1.camel@trentalancia.com> <1506798916.1659.3.camel@trentalancia.com> <1506811454.32049.1.camel@trentalancia.com> <2956012b-f494-40f2-75da-5d3dc9763d52@ieee.org> <8861CE28-A39E-4779-8322-F59D251F6528@trentalancia.com> Message-ID: To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com On Wed, Oct 4, 2017 at 2:41 AM, Guido Trentalancia via refpolicy wrote: > Hello Christopher. > > The latest version (v5) has been tested not only with valgrind but also with the Clang static analyzer and none of them reports any error. > > The Clang analyzer is the same one that was mentioned in the original bug report, I have used the latest version 5.0. > > I hope it helps. > > Regards, > > Guido > > Il 03 ottobre 2017 03:21:38 CEST, Chris PeBenito ha scritto: >>On 09/30/2017 06:44 PM, Guido Trentalancia via refpolicy wrote: >>> Avoid memory leakages in the fc_sort executable (now passes >>> all valgrind AND Clang static analyzer tests fine). >>> >>> Some NULL pointer checks with or without associated error >>> reporting. >>> >>> Some white space and comment formatting fixes. >>> >>> Optimization: avoid unnecessary operations (unnecessary >>> memory allocation/deallocation and list copying). >>> >>> Reverts 7821eb6f37d785ab6ac3bbdc39282c799ad22393 as such >>> trick is no longer needed, given that all memory leakages >>> have now been fixed. >>> >>> This is the fifth version of this patch. Please do not use >>> the first version as it introduces a serious bug. >>> >>> For reference, the original issue reported by the Cland >>> static analyzer is as follows: >>> >>> support/fc_sort.c:494:6: warning: Potential leak of memory >>> pointed to by 'head' >>> malloc(sizeof(file_context_bucket_t)); >> >>Bill, did your guys run this through their static analyzer? I'm >>inclined >>to merge this. >> >> >>> Signed-off-by: Guido Trentalancia >>> --- >>> support/fc_sort.c | 108 >>++++++++++++++++++++++++++++++++++-------------------- >>> 1 file changed, 69 insertions(+), 39 deletions(-) >>> >>> --- a/support/fc_sort.c 2017-09-30 02:44:18.137342226 +0200 >>> +++ b/support/fc_sort.c 2017-09-30 21:16:04.899069510 +0200 >>> @@ -46,6 +46,9 @@ typedef struct file_context_node { >>> >>> void file_context_node_destroy(file_context_node_t *x) >>> { >>> + if (!x) >>> + return; >>> + >>> free(x->path); >>> free(x->file_type); >>> free(x->context); >>> @@ -135,8 +138,6 @@ file_context_node_t *fc_merge(file_conte >>> file_context_node_t *temp; >>> file_context_node_t *jumpto; >>> >>> - >>> - >>> /* If a is a empty list, and b is not, >>> * set a as b and proceed to the end. */ >>> if (!a && b) >>> @@ -164,7 +165,6 @@ file_context_node_t *fc_merge(file_conte >>> fc_compare(a_current->next, >>> b_current) != -1) { >>> >>> - >>> temp = a_current->next; >>> a_current->next = b_current; >>> b_current = b_current->next; >>> @@ -177,7 +177,6 @@ file_context_node_t *fc_merge(file_conte >>> a_current = jumpto; >>> } >>> >>> - >>> /* if there is anything left in b to be inserted, >>> put it on the end */ >>> if (b_current) { >>> @@ -209,11 +208,12 @@ file_context_node_t *fc_merge(file_conte >>> */ >>> void fc_merge_sort(file_context_bucket_t *master) >>> { >>> - >>> - >>> file_context_bucket_t *current; >>> file_context_bucket_t *temp; >>> >>> + if (!master) >>> + return; >>> + >>> /* Loop until master is the only bucket left >>> * so that this will stop when master contains >>> * the sorted list. */ >>> @@ -222,28 +222,20 @@ void fc_merge_sort(file_context_bucket_t >>> >>> /* This loop merges buckets two-by-two. */ >>> while (current) { >>> - >>> if (current->next) { >>> - >>> current->data = >>> fc_merge(current->data, >>> current->next->data); >>> >>> - >>> - >>> temp = current->next; >>> current->next = current->next->next; >>> >>> free(temp); >>> - >>> } >>> >>> - >>> current = current->next; >>> } >>> } >>> - >>> - >>> } >>> >>> >>> @@ -307,6 +299,25 @@ void fc_fill_data(file_context_node_t *f >>> } >>> } >>> >>> + >>> + >>> +/* fc_free_file_context_node_list >>> + * Free the memory allocated to the linked list and its elements. >>> + */ >>> +void fc_free_file_context_node_list(struct file_context_node *node) >>> +{ >>> + struct file_context_node *next; >>> + >>> + while (node) { >>> + next = node->next; >>> + file_context_node_destroy(node); >>> + free(node); >>> + node = next; >>> + } >>> +} >>> + >>> + >>> + >>> /* main >>> * This program takes in two arguments, the input filename and the >>> * output filename. The input file should be syntactically >>correct. >>> @@ -328,7 +339,6 @@ int main(int argc, char *argv[]) >>> >>> FILE *in_file, *out_file; >>> >>> - >>> /* Check for the correct number of command line arguments. */ >>> if (argc < 2 || argc > 3) { >>> fprintf(stderr, "Usage: %s []\n",argv[0]); >>> @@ -348,24 +358,33 @@ int main(int argc, char *argv[]) >>> >>> /* Initialize the head of the linked list. */ >>> head = current = >>(file_context_node_t*)malloc(sizeof(file_context_node_t)); >>> + if (!head) { >>> + fprintf(stderr, "Error: failure allocating memory.\n"); >>> + return 1; >>> + } >>> head->next = NULL; >>> + head->path = NULL; >>> + head->file_type = NULL; >>> + head->context = NULL; >>> >>> /* Parse the file into a file_context linked list. */ >>> line_buf = NULL; >>> >>> while ( getline(&line_buf, &buf_len, in_file) != -1 ){ >>> line_len = strlen(line_buf); >>> + >>> if( line_len == 0 || line_len == 1) >>> continue; >>> + >>> /* Get rid of whitespace from the front of the line. */ >>> for (i = 0; i < line_len; i++) { >>> if (!isspace(line_buf[i])) >>> break; >>> } >>> >>> - >>> if (i >= line_len) >>> continue; >>> + >>> /* Check if the line isn't empty and isn't a comment */ >>> if (line_buf[i] == '#') >>> continue; >>> @@ -373,7 +392,9 @@ int main(int argc, char *argv[]) >>> /* We have a valid line - allocate a new node. */ >>> temp = (file_context_node_t >>*)malloc(sizeof(file_context_node_t)); >>> if (!temp) { >>> + free(line_buf); >>> fprintf(stderr, "Error: failure allocating memory.\n"); >>> + fc_free_file_context_node_list(head); >>> return 1; >>> } >>> temp->next = NULL; >>> @@ -382,19 +403,15 @@ int main(int argc, char *argv[]) >>> /* Parse out the regular expression from the line. */ >>> start = i; >>> >>> - >>> while (i < line_len && (!isspace(line_buf[i]))) >>> i++; >>> finish = i; >>> >>> - >>> regex_len = finish - start; >>> >>> if (regex_len == 0) { >>> file_context_node_destroy(temp); >>> free(temp); >>> - >>> - >>> continue; >>> } >>> >>> @@ -402,13 +419,14 @@ int main(int argc, char *argv[]) >>> if (!temp->path) { >>> file_context_node_destroy(temp); >>> free(temp); >>> + free(line_buf); >>> fprintf(stderr, "Error: failure allocating memory.\n"); >>> + fc_free_file_context_node_list(head); >>> return 1; >>> } >>> >>> /* Get rid of whitespace after the regular expression. */ >>> for (; i < line_len; i++) { >>> - >>> if (!isspace(line_buf[i])) >>> break; >>> } >>> @@ -420,18 +438,21 @@ int main(int argc, char *argv[]) >>> } >>> >>> /* Parse out the type from the line (if it >>> - * is there). */ >>> + * is there). */ >>> if (line_buf[i] == '-') { >>> temp->file_type = (char *)malloc(sizeof(char) * 3); >>> if (!(temp->file_type)) { >>> + file_context_node_destroy(temp); >>> + free(temp); >>> + free(line_buf); >>> fprintf(stderr, "Error: failure allocating memory.\n"); >>> + fc_free_file_context_node_list(head); >>> return 1; >>> } >>> >>> if( i + 2 >= line_len ) { >>> file_context_node_destroy(temp); >>> free(temp); >>> - >>> continue; >>> } >>> >>> @@ -448,7 +469,6 @@ int main(int argc, char *argv[]) >>> } >>> >>> if (i == line_len) { >>> - >>> file_context_node_destroy(temp); >>> free(temp); >>> continue; >>> @@ -467,24 +487,23 @@ int main(int argc, char *argv[]) >>> if (!temp->context) { >>> file_context_node_destroy(temp); >>> free(temp); >>> + free(line_buf); >>> fprintf(stderr, "Error: failure allocating memory.\n"); >>> + fc_free_file_context_node_list(head); >>> return 1; >>> } >>> >>> /* Set all the data about the regular >>> - * expression. */ >>> + * expression. */ >>> fc_fill_data(temp); >>> >>> /* Link this line of code at the end of >>> - * the linked list. */ >>> + * the linked list. */ >>> current->next = temp; >>> current = current->next; >>> lines++; >>> - >>> - >>> - free(line_buf); >>> - line_buf = NULL; >>> } >>> + free(line_buf); >>> fclose(in_file); >>> >>> /* Create the bucket linked list from the earlier linked list. */ >>> @@ -492,6 +511,12 @@ int main(int argc, char *argv[]) >>> bcurrent = master = >>> (file_context_bucket_t *) >>> malloc(sizeof(file_context_bucket_t)); >>> + if (!bcurrent) { >>> + printf >>> + ("Error: failure allocating memory.\n"); >>> + fc_free_file_context_node_list(head); >>> + return -1; >>> + } >>> bcurrent->next = NULL; >>> bcurrent->data = NULL; >>> >>> @@ -512,25 +537,33 @@ int main(int argc, char *argv[]) >>> if (!(bcurrent->next)) { >>> printf >>> ("Error: failure allocating memory.\n"); >>> - exit(-1); >>> + free(head); >>> + fc_free_file_context_node_list(current); >>> + fc_merge_sort(master); >>> + fc_free_file_context_node_list(master->data); >>> + free(master); >>> + return -1; >>> } >>> >>> /* Make sure the new bucket thinks it's the end of the >>> - * list. */ >>> + * list. */ >>> bcurrent->next->next = NULL; >>> >>> bcurrent = bcurrent->next; >>> } >>> - >>> } >>> >>> /* Sort the bucket list. */ >>> fc_merge_sort(master); >>> >>> + free(head); >>> + >>> /* Open the output file. */ >>> if (output_name) { >>> if (!(out_file = fopen(output_name, "w"))) { >>> printf("Error: failure opening output file for write.\n"); >>> + fc_free_file_context_node_list(master->data); >>> + free(master); >>> return -1; >>> } >>> } else { >>> @@ -539,6 +572,7 @@ int main(int argc, char *argv[]) >>> >>> /* Output the sorted file_context linked list to the output file. >>*/ >>> current = master->data; >>> + >>> while (current) { >>> /* Output the path. */ >>> fprintf(out_file, "%s\t\t", current->path); >>> @@ -551,14 +585,10 @@ int main(int argc, char *argv[]) >>> /* Output the context. */ >>> fprintf(out_file, "%s\n", current->context); >>> >>> - /* Remove the node. */ >>> - temp = current; >>> current = current->next; >>> - >>> - file_context_node_destroy(temp); >>> - free(temp); >>> - >>> } >>> + >>> + fc_free_file_context_node_list(master->data); >>> free(master); >>> >>> if (output_name) { >>> _______________________________________________ >>> refpolicy mailing list >>> refpolicy at oss.tresys.com >>> http://oss.tresys.com/mailman/listinfo/refpolicy >>> > > _______________________________________________ > refpolicy mailing list > refpolicy at oss.tresys.com > http://oss.tresys.com/mailman/listinfo/refpolicy I would go ahead and merge this, and it seems to be the proper fix for the error reported via clang and it works on Android as expected. (unfortunately my @intel email address sometimes has issues with mailing lists, but please use it) (Take any of the -by lines you want, I really don't care about that stuff) Just make sure either the applier or author (v6) fixes: Applying: fc_sort: memory leakages .git/rebase-apply/patch:269: trailing whitespace. ("Error: failure allocating memory.\n"); warning: 1 line adds whitespace errors. Always check your patches with something like * git diff --check * git show HEAD --check prior to sending. The bug does seem fixed per my clang version of 3.8: Patch Applied: $ scan-build gcc -o go support/fc_sort.c scan-build: Using '/usr/lib/llvm-3.8/bin/clang' for static analysis scan-build: Removing directory '/tmp/scan-build-2017-10-04-104851-19628-1' because it contains no reports. scan-build: No bugs found. Without Patch: support/fc_sort.c:494:6: warning: Potential leak of memory pointed to by 'head' malloc(sizeof(file_context_bucket_t)); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 warning generated. scan-build: 1 bug found. scan-build: Run 'scan-view /tmp/scan-build-2017-10-04-104902-19662-1' to examine bug reports. I also manually ran the fc_sort against the Android build artifacts to verify that they are the same via below: Produced via Android build (old fc_sort) $ md5sum $OUT/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.sorted.tmp 27d0c1b0d0a516fa9019917b31d3f196 /home/wcrobert/workspace/aosp/out/target/product/hikey/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.sorted.tmp The new file with the patched fc_sort: ~/workspace/refpolicy/fc_sort $OUT/obj/ETC/file_contexts.bin_intermediates/file_contexts.device.tmp file_contexts.device.sorted.tmp $ md5sum file_contexts.device.sorted.tmp 27d0c1b0d0a516fa9019917b31d3f196 file_contexts.device.sorted.tmp Valgrind also reports no leaks or memory issues Once this is merged, ill go ahead and update AOSPs usage of fc_sort unless someone from Google beats me to it. FYI Ill be on vacation for a week, so I won't be reachable on this matter. Thanks for the patch! Bill