zhenwei pi 85bd23f3dc nvmet: fix uninitialized work for zero kato
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
0d3b6a8d213a), ka_work still has a chance to run (called by
nvmet_start_ctrl).

Fixes: 0d3b6a8d213a ("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>
2020-10-22 15:27:14 +02:00
..
2020-10-12 10:00:51 -07:00
2020-08-02 18:26:51 +03:00
2020-09-10 09:32:31 -06:00
2020-10-13 12:12:44 -07:00
2020-10-12 13:26:49 -07:00
2020-10-13 09:37:02 -07:00
2020-10-13 09:37:02 -07:00
2020-09-07 16:13:06 +02:00
2020-09-15 16:20:43 -07:00
2020-10-13 12:12:44 -07:00
2020-10-13 12:12:44 -07:00
2020-08-05 19:24:27 -07:00
2020-10-13 13:04:41 -07:00
2020-09-28 12:17:36 +02:00
2020-08-28 10:15:33 -07:00
2020-10-13 12:12:44 -07:00
2020-10-13 12:12:44 -07:00
2020-10-13 12:12:44 -07:00
2020-09-29 17:21:54 +02:00
2020-10-06 12:00:52 -07:00
2020-10-09 11:38:07 -07:00
2020-08-14 16:00:09 -07:00
2020-10-13 12:12:44 -07:00
2020-10-13 15:05:05 -06:00
2020-10-09 18:05:12 -07:00
2020-10-13 09:37:02 -07:00
2020-10-13 12:12:44 -07:00
2020-09-15 13:52:14 +02:00
2020-09-25 16:53:02 +02:00
2020-10-06 12:38:28 +10:00