From: Jens Axboe <axboe@kernel.dk>
To: Fengguang Wu <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
LKP <lkp@01.org>
Subject: Re: [bdi_unregister] 165a5e22fa INFO: task swapper:1 blocked for more than 120 seconds.
Date: Sun, 5 Mar 2017 08:12:30 -0700 [thread overview]
Message-ID: <912e4814-eeee-a959-c049-2aa22bb80781@kernel.dk> (raw)
In-Reply-To: <20170305022111.yqtwyd6ognmco4gx@wfg-t540p.sh.intel.com>
On 03/04/2017 07:21 PM, Fengguang Wu wrote:
> Hi Jan,
>
> FYI next-20170303 is good while mainline is bad with this error.
> The attached reproduce-* may help reproduce the issue.
What's the test case here? It's Sunday, we need to make a quick
decision on whether to revert this patch or not. I'm inclined to
do so.
Jan?
--
Jens Axboe
next prev parent reply other threads:[~2017-03-05 15:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 2:21 [bdi_unregister] 165a5e22fa INFO: task swapper:1 blocked for more than 120 seconds Fengguang Wu
2017-03-05 2:21 ` Fengguang Wu
2017-03-05 2:24 ` [bdi_unregister] 165a5e22fa BUG kmalloc-512 (Not tainted): Poison overwritten Fengguang Wu
2017-03-05 2:24 ` Fengguang Wu
2017-03-05 15:12 ` Jens Axboe [this message]
2017-03-06 1:19 ` [bdi_unregister] 165a5e22fa INFO: task swapper:1 blocked for more than 120 seconds Fengguang Wu
2017-03-06 1:19 ` Fengguang Wu
2017-03-06 10:27 ` Jan Kara
2017-03-06 10:27 ` Jan Kara
2017-03-06 12:01 ` Jan Kara
2017-03-06 12:01 ` Jan Kara
2017-03-06 14:35 ` James Bottomley
2017-03-06 14:35 ` James Bottomley
2017-03-06 15:14 ` Jan Kara
2017-03-06 15:14 ` Jan Kara
2017-03-06 15:44 ` James Bottomley
2017-03-06 15:44 ` James Bottomley
2017-03-06 16:13 ` Jan Kara
2017-03-06 16:13 ` Jan Kara
2017-03-06 17:25 ` James Bottomley
2017-03-06 17:25 ` James Bottomley
2017-03-07 14:41 ` Jan Kara
2017-03-07 14:41 ` Jan Kara
2017-03-07 16:10 ` James Bottomley
2017-03-07 16:10 ` James Bottomley
2017-03-07 16:26 ` Jan Kara
2017-03-07 16:26 ` Jan Kara
2017-03-08 9:59 ` Jan Kara
2017-03-08 9:59 ` Jan Kara
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=912e4814-eeee-a959-c049-2aa22bb80781@kernel.dk \
--to=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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 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.