Skip to contentSkip to conversation

Patch "dev/dax: fix uninitialized variable build warning" has been added to the 4.14-stable tree

PATCH [email protected] 1 participant 1 message Dec 18, 2017

Subsystems (2)
lore
Share & tools
lore

[email protected]

author maintainer Applied
#0 lore raw

This is a note to let you know that I've just added the patch titled

dev/dax: fix uninitialized variable build warning

to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
dev-dax-fix-uninitialized-variable-build-warning.patch
and it can be found in the queue-4.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

Quoted 1 line

From foo@baz Mon Dec 18 13:28:59 CET 2017

From: Ross Zwisler <[email protected]>
Date: Wed, 18 Oct 2017 12:21:55 -0600
Subject: dev/dax: fix uninitialized variable build warning

From: Ross Zwisler <[email protected]>

[ Upstream commit 0a3ff78699d1817e711441715d22665475466036 ]

Fix this build warning:

warning: 'phys' may be used uninitialized in this function [-Wuninitialized]

As reported here:

https://lkml.org/lkml/2017/10/16/152
http://kisskb.ellerman.id.au/kisskb/buildresult/13181373/log/

---
 drivers/dax/device.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/dax/device.c +2 -1
@@ -222,7 +222,8 @@ __weak phys_addr_t dax_pgoff_to_phys(str
 		unsigned long size)
 {
 	struct resource *res;
-	phys_addr_t phys;
+	/* gcc-4.6.3-nolibc for i386 complains that this is uninitialized */
+	phys_addr_t uninitialized_var(phys);
 	int i;
 
 	for (i = 0; i < dev_dax->num_resources; i++) {

Patches currently in stable-queue which might be from [email protected] are

queue-4.14/dev-dax-fix-uninitialized-variable-build-warning.patch