zhenwei pi b6addb4a03 nvmet: fix uninitialized work for zero kato ... [ Upstream commit 85bd23f3dc ] When connecting a controller with a zero kato value using the following command line nvme connect -t tcp -n NQN -a ADDR -s PORT --keep-alive-tmo=0 the warning below can be reproduced: WARNING: CPU: 1 PID: 241 at kernel/workqueue.c:1627 __queue_delayed_work+0x6d/0x90 with trace: mod_delayed_work_on+0x59/0x90 nvmet_update_cc+0xee/0x100 [nvmet] nvmet_execute_prop_set+0x72/0x80 [nvmet] nvmet_tcp_try_recv_pdu+0x2f7/0x770 [nvmet_tcp] nvmet_tcp_io_work+0x63f/0xb2d [nvmet_tcp] ... This is caused by queuing up an uninitialized work. Althrough the keep-alive timer is disabled during allocating the controller (fixed in 0d3b6a8d21), ka_work still has a chance to run (called by nvmet_start_ctrl). Fixes: 0d3b6a8d21 ("nvmet: Disable keep-alive timer when kato is cleared to 0h") Signed-off-by: zhenwei pi <pizhenwei@bytedance.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sasha Levin <sashal@kernel.org>		2020-10-30 10:38:25 +01:00
..
admin-cmd.c	nvmet: fix data units read and written counters in SMART log	2019-10-05 13:09:52 +02:00
configfs.c
core.c	nvmet: fix uninitialized work for zero kato	2020-10-30 10:38:25 +01:00
discovery.c
fabrics-cmd.c
fc.c	nvmet-fc: Fix a missed _irqsave version of spin_lock in 'nvmet_fc_fod_op_done()'	2020-09-09 19:04:26 +02:00
fcloop.c	nvme-fc: Revert "add module to ops template to allow module references"	2020-04-17 10:48:45 +02:00
io-cmd-bdev.c	nvmet: fix data_len to 0 for bdev-backed write_zeroes	2019-06-25 11:35:58 +08:00
io-cmd-file.c	nvmet: avoid integer overflow in the discard code	2019-12-01 09:16:29 +01:00
Kconfig
loop.c	nvmet-loop: Flush nvme_delete_wq when removing the port	2019-09-06 10:21:55 +02:00
Makefile
nvmet.h
rdma.c	nvmet-rdma: fix double free of rdma queue	2020-10-01 13:14:41 +02:00