From: Hauke Mehrtens <hauke@hauke-m.de>
To: Mark Brown <broonie@kernel.org>
Cc: axboe@kernel.dk, linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: lantiq-ssc: Fix warning by using WQ_MEM_RECLAIM
Date: Fri, 17 Jul 2020 23:54:58 +0200 [thread overview]
Message-ID: <59df62e3-33fd-4615-ac98-bd426e80be3f@hauke-m.de> (raw)
In-Reply-To: <20200715094836.GA5431@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 930 bytes --]
On 7/15/20 11:48 AM, Mark Brown wrote:
> On Wed, Jul 15, 2020 at 01:02:34AM +0200, Hauke Mehrtens wrote:
>
>> This fixes the following warning:
>> [ 2.972635] ------------[ cut here ]------------
>> [ 2.975956] WARNING: CPU: 1 PID: 17 at kernel/workqueue.c:2614 check_flush_dependency+0x168/0x184
>> [ 2.984752] workqueue: WQ_MEM_RECLAIM kblockd:blk_mq_run_work_fn is flushing !WQ_MEM_RECLAIM 1e100800.spi:0x0
>> [ 2.984759] Modules linked in:
>
> Please think hard before including complete backtraces in upstream
> reports, they are very large and contain almost no useful information
> relative to their size so often obscure the relevant content in your
> message. If part of the backtrace is usefully illustrative (it often is
> for search engines if nothing else) then it's usually better to pull out
> the relevant sections.
>
Ok, I will send a v2 with an updated commit message.
Hauke
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-07-17 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 23:02 [PATCH] spi: lantiq-ssc: Fix warning by using WQ_MEM_RECLAIM Hauke Mehrtens
2020-07-15 9:48 ` Mark Brown
2020-07-17 21:54 ` Hauke Mehrtens [this message]
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=59df62e3-33fd-4615-ac98-bd426e80be3f@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=linux-spi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).