commit | 21d61d18f9682de69d7cc1632003fb4e476af43a | [log] [tgz] |
---|---|---|
author | David Gibson <david@gibson.dropbear.id.au> | Tue Jun 08 15:28:55 2021 +1000 |
committer | David Gibson <david@gibson.dropbear.id.au> | Tue Jun 08 16:32:59 2021 +1000 |
tree | a7633f9f50b97288500487b403f2cf9ea00f9efd | |
parent | 4c2ef8f4d14ca411b41b9c6891028d58d2079bf7 [diff] |
Fix CID 1461557 Coverity gets a bit confused by loading fdt_size_dt_strings() and using it in a memmove(). In fact this is safe because the callers have verified this information (via FDT_RW_PROBE() in fdt_pack() or construction in fdt_open_into()). Passing in strings_size like we already do struct_size seems to get Coverity to follow what's going on here. Signed-off-by: David Gibson <david@gibson.dropbear.id.au>