Hello I reproduced this issue on the linux-block/for-next, pls help check it, feel free to let me know if you need info/test, thanks.
These reports are making me tired... Should we just remove MEM_RECLAIM from all nvme/nvmet workqueues are be done with it? The only downside is that nvme reset/error-recovery will also be susceptible for low-memory situation... Christoph, Keith, what are your thoughts?
