diff options
| author | James Smart <[email protected]> | 2017-12-21 22:15:47 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2017-12-29 09:37:21 +0000 |
| commit | 254beb84faccbe2f4eda0b51924857bdfb679969 (patch) | |
| tree | 35c48cbe81577c5e43fe369032e9a2efa4c3c6b3 /fs/jbd2/commit.c | |
| parent | nvme-mpath: fix last path removal during traffic (diff) | |
| download | kernel-254beb84faccbe2f4eda0b51924857bdfb679969.tar.gz kernel-254beb84faccbe2f4eda0b51924857bdfb679969.zip | |
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 <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions