fix newer coverity issues 12023, 12024, and 12025
ldclt.c: 12023 Ignoring number of bytes read The number of bytes copied into the buffer can be smaller than the requested number and the buffer can potentially be accessed out of range. In basicInit: Value returned from a function and indicating the number of bytes read is ignored.
roles_cache.c: 12024 Resource leak The system resource will not be reclaimed and reused, reducing the future availability of the resource. In roles_cache_create_object_from_entry: Leak of memory or pointers to system resources
dblayer.c: 12025 Wrong sizeof argument The wrong sizeof value is used in an expression or as argument to a function. The result is an incorrect value that may cause unexpected program behaviors. In read_metadata: The sizeof operator is invoked on the wrong argument
master: commit f702868012ac1f9deb1cb92d51cdfd793353e836 Author: Noriko Hosoi nhosoi@redhat.com Date: Mon Sep 30 12:45:15 2013 -0700
389-ds-base-1.3.1: commit 99f7b65e4bd35ce5d2c24a05178cfca4a44645db Author: Noriko Hosoi nhosoi@redhat.com Date: Mon Sep 30 12:45:15 2013 -0700
389-ds-base-1.3.0: commit aa19f9ad2d2d1ee58fa2a0da3b6119a95ea47733 Author: Noriko Hosoi nhosoi@redhat.com Date: Mon Sep 30 12:45:15 2013 -0700
389-ds-base-1.2.11: commit 2d588df1ab832d5027719c25a4b2477de22b5839 Author: Noriko Hosoi nhosoi@redhat.com Date: Mon Sep 30 12:45:15 2013 -0700
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1014351
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1014354
Metadata Update from @rmeggins: - Issue set to the milestone: 1.2.11.23
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/877
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)