diff options
| author | James Smart <jsmart2021@gmail.com> | 2017-12-21 14:15:47 -0800 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2017-12-29 10:37:21 +0100 |
| commit | 254beb84faccbe2f4eda0b51924857bdfb679969 (patch) | |
| tree | 35c48cbe81577c5e43fe369032e9a2efa4c3c6b3 /drivers/nvme | |
| parent | 479a322fb729d657d34706ccf8dd12916f36628f (diff) | |
| download | linux-254beb84faccbe2f4eda0b51924857bdfb679969.tar.bz2 | |
nvme-fcloop: avoid possible uninitialized variable warning
The kbuild test robot send mail of a potential use of an uninitialized
variable - "tport" in fcloop_delete_targetport() which then calls
__targetport_unreg() which uses the variable. It will never be the
case it is uninitialized as the call to __targetport_unreg() only
occurs if there is a valid nport pointer. And at the time the nport
pointer is assigned, the tport variable is set.
Remove the warning by assigning a NULL value initially.
Signed-off-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/nvme')
| -rw-r--r-- | drivers/nvme/target/fcloop.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/nvme/target/fcloop.c b/drivers/nvme/target/fcloop.c index 7b75d9de55ab..6a018a0bd6ce 100644 --- a/drivers/nvme/target/fcloop.c +++ b/drivers/nvme/target/fcloop.c @@ -1085,7 +1085,7 @@ fcloop_delete_target_port(struct device *dev, struct device_attribute *attr, const char *buf, size_t count) { struct fcloop_nport *nport = NULL, *tmpport; - struct fcloop_tport *tport; + struct fcloop_tport *tport = NULL; u64 nodename, portname; unsigned long flags; int ret; |