drivers/nvme/target/fcloop.c:1080:9: warning: 'tport' may be used uninitialized in this function

From: kbuild test robot
Date: Wed Dec 06 2017 - 01:08:30 EST


tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 328b4ed93b69a6f2083d52f31a240a09e5de386a
commit: fddc9923c6d41de9fe7b1f323a3cece53e046c88 nvme-fcloop: fix port deletes and callbacks
date: 2 months ago
config: i386-randconfig-h1-12061225 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout fddc9923c6d41de9fe7b1f323a3cece53e046c88
# save the attached .config to linux build tree
make ARCH=i386

Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings

All warnings (new ones prefixed by >>):

drivers/nvme/target/fcloop.c: In function 'fcloop_delete_target_port':
>> drivers/nvme/target/fcloop.c:1080:9: warning: 'tport' may be used uninitialized in this function [-Wmaybe-uninitialized]
return nvmet_fc_unregister_targetport(tport->targetport);
^
drivers/nvme/target/fcloop.c:1088:23: note: 'tport' was declared here
struct fcloop_tport *tport;
^

vim +/tport +1080 drivers/nvme/target/fcloop.c

1073
1074 static int
1075 __targetport_unreg(struct fcloop_nport *nport, struct fcloop_tport *tport)
1076 {
1077 if (!tport)
1078 return -EALREADY;
1079
> 1080 return nvmet_fc_unregister_targetport(tport->targetport);
1081 }
1082

---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation

Attachment: .config.gz
Description: application/gzip