On Wed, Oct 18, 2017 at 8:40 AM, Ross Zwisler
Fix this build warning:
warning: 'phys' may be used uninitialized in this function
As reported here:
This should have no functional change because you can only get into the if
statement in dax_pgoff_to_phys() that is complaining about 'phys' being
uninitialized if you broke out early in the above loop, in which case
'phys' will be set.
Then the compiler is wrong.
Signed-off-by: Ross Zwisler <ross.zwisler(a)linux.intel.com>
drivers/dax/device.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dax/device.c b/drivers/dax/device.c
index e9f3b3e..4aca0a2 100644
@@ -222,7 +222,7 @@ __weak phys_addr_t dax_pgoff_to_phys(struct dev_dax *dev_dax, pgoff_t
unsigned long size)
struct resource *res;
- phys_addr_t phys;
+ phys_addr_t phys = 0;
We have uninitialized_var() for silencing the compiler, and since the
report is bogus we might note with a comment which gcc had a problem
with this routine.