From: Sagi Grimberg <sagi@grimberg.me>
To: Yi Zhang <yi.zhang@redhat.com>,
linux-block <linux-block@vger.kernel.org>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>
Subject: Re: [bug report] blktests nvme/tcp triggered WARNING at kernel/workqueue.c:2628 check_flush_dependency+0x110/0x14c
Date: Sun, 10 Jul 2022 12:41:33 +0300 [thread overview]
Message-ID: <5ce566fd-f871-48dc-1cb7-30b745c58f05@grimberg.me> (raw)
In-Reply-To: <CAHj4cs86Dm577NK-C+bW6=+mv2V3KOpQCG0Vg6xZrSGzNijX4g@mail.gmail.com>
> 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?
next prev parent reply other threads:[~2022-07-10 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 16:03 [bug report] blktests nvme/tcp triggered WARNING at kernel/workqueue.c:2628 check_flush_dependency+0x110/0x14c Yi Zhang
2022-07-10 9:41 ` Sagi Grimberg [this message]
2022-07-19 16:08 ` Yi Zhang
2022-07-20 6:18 ` Christoph Hellwig
2022-07-21 22:13 ` Sagi Grimberg
2022-07-22 4:46 ` Christoph Hellwig
2022-07-24 8:21 ` Sagi Grimberg
2022-07-29 7:37 ` Yi Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ce566fd-f871-48dc-1cb7-30b745c58f05@grimberg.me \
--to=sagi@grimberg.me \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=yi.zhang@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.