Re: [LKP] [workqueue] 4d43d395fe: WARNING:at_kernel/workqueue.c:#__flush_work

On 3/4/2019 10:21 AM, Sagi Grimberg wrote: Forwarding to NMVE people: kernel test robot found that flush_work(&ctrl->async_event_work) is called from nvmet_ctrl_free() without INIT_WORK(&ctrl->async_event_work, nvmet_async_event_work) after ctrl was allocated (probably initialized with 0). Wil

Re: [LKP] [workqueue] 4d43d395fe: WARNING:at_kernel/workqueue.c:#__flush_work

Forwarding to NMVE people: kernel test robot found that flush_work(&ctrl->async_event_work) is called from nvmet_ctrl_free() without INIT_WORK(&ctrl->async_event_work, nvmet_async_event_work) after ctrl was allocated (probably initialized with 0). Will you make sure that INIT_WORK() is always

Re: [LKP] [workqueue] 4d43d395fe: WARNING:at_kernel/workqueue.c:#__flush_work

Forwarding to NMVE people: kernel test robot found that flush_work(&ctrl->async_event_work) is called from nvmet_ctrl_free() without INIT_WORK(&ctrl->async_event_work, nvmet_async_event_work) after ctrl was allocated (probably initialized with 0). Will you make sure that INIT_WORK() is always call