From: Jason Gunthorpe <jgg@nvidia.com>
To: Zhu Yanjun <yanjun.zhu@linux.dev>
Cc: bvanassche@acm.org, leon@kernel.org, linux-rdma@vger.kernel.org,
shinichiro.kawasaki@wdc.com,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH 1/1] RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency
Date: Mon, 19 Aug 2024 15:38:21 -0300 [thread overview]
Message-ID: <20240819183821.GA3487760@nvidia.com> (raw)
In-Reply-To: <20240817084244.536397-1-yanjun.zhu@linux.dev>
On Sat, Aug 17, 2024 at 10:42:44AM +0200, Zhu Yanjun wrote:
> When workqueue_flush is invoked, WQ_MEM_RECLAIM is checked to avoid
> errors.
Include backtraces please, these things are tricky and we often have
to go back and figure out why.
Explaine exactly why it is needed with traces in the commit message
and summarize in a comment.
Jason
next prev parent reply other threads:[~2024-08-19 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 8:42 [PATCH 1/1] RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency Zhu Yanjun
2024-08-19 18:38 ` Jason Gunthorpe [this message]
2024-08-19 22:38 ` Zhu Yanjun
2024-08-19 19:28 ` Bart Van Assche
2024-08-19 22:42 ` Zhu Yanjun
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=20240819183821.GA3487760@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yanjun.zhu@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox