btrfs-progs: initialize save_ptr prior to strtok_r
The coverity runs had a false positive complaining that save_ptr is uninitialized in the call to strtok_r. Turns out that under the covers glibc was doing enough to confuse the checker about what was being called. Just to keep the noise down, do a harmless initialization, with a comment as to why. Signed-off-by: Eric Sandeen <sandeen@redhat.com>
This commit is contained in:
parent
fb631862c9
commit
e7cce77a56
|
@ -67,7 +67,7 @@ static int parse_one_profile(const char *profile, u64 *flags)
|
|||
static int parse_profiles(char *profiles, u64 *flags)
|
||||
{
|
||||
char *this_char;
|
||||
char *save_ptr;
|
||||
char *save_ptr = NULL; /* Satisfy static checkers */
|
||||
|
||||
for (this_char = strtok_r(profiles, "|", &save_ptr);
|
||||
this_char != NULL;
|
||||
|
@ -136,7 +136,7 @@ static int parse_filters(char *filters, struct btrfs_balance_args *args)
|
|||
{
|
||||
char *this_char;
|
||||
char *value;
|
||||
char *save_ptr;
|
||||
char *save_ptr = NULL; /* Satisfy static checkers */
|
||||
|
||||
if (!filters)
|
||||
return 0;
|
||||
|
|
Loading…
Reference in a new issue