From: Tejun Heo <tj@kernel.org>
To: Zdenek Sojka <zsojka@seznam.cz>
Cc: linux-kernel@vger.kernel.org, jiangshanlai@gmail.com
Subject: Re: workqueue: PF_MEMALLOC task 14771(cc1plus) is flushing !WQ_MEM_RECLAIM events:gen6_pm_rps_work
Date: Thu, 3 Oct 2019 09:49:44 -0700 [thread overview]
Message-ID: <20191003164944.GB3247445@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <12X.2yh9.1rKbaucucGw.1TZ6EI@seznam.cz>
Hello,
On Thu, Sep 26, 2019 at 09:06:58AM +0200, Zdenek Sojka wrote:
> I've hit the following dmesg with a 5.3.1 kernel; it looks similar to https://lkml.org/lkml/2019/8/28/754 , which should have been fixed as noted in https://lkml.org/lkml/2019/8/28/763 (if the patch is in the 5.3 release)
This isn't a wq problem per-se. Can you repost w/ drm folks cc'd?
Thanks.
--
tejun
prev parent reply other threads:[~2019-10-03 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 7:06 workqueue: PF_MEMALLOC task 14771(cc1plus) is flushing !WQ_MEM_RECLAIM events:gen6_pm_rps_work Zdenek Sojka
2019-10-03 16:49 ` Tejun Heo [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=20191003164944.GB3247445@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zsojka@seznam.cz \
/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).