From: Stefan Priebe <s.priebe@profihost.ag>
To: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Cc: kent.overstreet@gmail.com, Eric Wheeler <bcache@lists.ewheeler.net>
Subject: bcache_writeback task blocked for more ...
Date: Sat, 18 Jul 2015 07:27:30 +0200 [thread overview]
Message-ID: <55A9E3C2.4040608@profihost.ag> (raw)
Hi List,
while running bcache on 3.18.18 and having added the known patches from
the list i still get blocked bcache_writeback tasks.
The kernel does now show any stack trace on his own.
The relevant tasks look like this:
[: ~]# cat /proc/769/stack
[<ffffffffa01e9685>] closure_sync+0x25/0x90 [bcache]
[<ffffffffa01feb9c>] read_dirty+0x31c/0x410 [bcache]
[<ffffffffa01fee94>] bch_writeback_thread+0x204/0x400 [bcache]
[<ffffffff81090af9>] kthread+0xc9/0xe0
[<ffffffff815f9008>] ret_from_fork+0x58/0x90
[<ffffffffffffffff>] 0xffffffffffffffff
[: ~]# cat /proc/769/stack
[<ffffffffa01e9685>] closure_sync+0x25/0x90 [bcache]
[<ffffffffa01feb9c>] read_dirty+0x31c/0x410 [bcache]
[<ffffffffa01fee94>] bch_writeback_thread+0x204/0x400 [bcache]
[<ffffffff81090af9>] kthread+0xc9/0xe0
[<ffffffff815f9008>] ret_from_fork+0x58/0x90
[<ffffffffffffffff>] 0xffffffffffffffff
[: ~]# cat /proc/773/stack
[<ffffffff810b7601>] down+0x41/0x50
[<ffffffffa01fea78>] read_dirty+0x1f8/0x410 [bcache]
[<ffffffffa01fee94>] bch_writeback_thread+0x204/0x400 [bcache]
[<ffffffff81090af9>] kthread+0xc9/0xe0
[<ffffffff815f9008>] ret_from_fork+0x58/0x90
[<ffffffffffffffff>] 0xffffffffffffffff
[: ~]# cat /proc/783/stack
[<ffffffffa01e9685>] closure_sync+0x25/0x90 [bcache]
[<ffffffffa01feb9c>] read_dirty+0x31c/0x410 [bcache]
[<ffffffffa01fee94>] bch_writeback_thread+0x204/0x400 [bcache]
[<ffffffff81090af9>] kthread+0xc9/0xe0
[<ffffffff815f9008>] ret_from_fork+0x58/0x90
[<ffffffffffffffff>] 0xffffffffffffffff
Greets,
Stefan
reply other threads:[~2015-07-18 5:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55A9E3C2.4040608@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=bcache@lists.ewheeler.net \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@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).