public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Wiele <jan@wiele.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Hang in bcache/qemu
Date: Thu, 19 Jan 2017 15:06:15 +0100	[thread overview]
Message-ID: <2468407.km8j8RHp0H@j-t460p> (raw)
In-Reply-To: <20170119134244.f6bydzrfsghq57ll@moria.home.lan>

Am Donnerstag, 19. Januar 2017, 04:42:44 CET schrieb Kent Overstreet:
> On Thu, Jan 19, 2017 at 01:22:47PM +0100, Jan Wiele wrote:
> > Am Mittwoch, 18. Januar 2017, 09:48:30 CET schrieb Andre Noll:
> > > On Wed, Jan 18, 04:35, Kai Krakow wrote
> > > 
> > > FWIW, I'm seeing this as well on different hardware, and with both
> > > deadline and CFQ, so it's not a scheduler issue. The problem seems to
> > > be the bcache writeback thread calling down_write(&dc->writeback_lock)
> > > while already holding this lock.
> > 
> > Yes, the bug doesn't get triggered when the caching mechanism is set to
> > writethrough.
> 
> Is there something else blocked that's holding writeback_lock?

I'm not seeing any other blocked tasks in the kernel log, if it is that what 
you mean. 

If you could provide me with some instructions to follow on a hang, I will try 
to reproduce it next weekend.

      reply	other threads:[~2017-01-19 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 17:34 Hang in bcache/qemu Jan Wiele
2017-01-18  3:35 ` Kai Krakow
2017-01-18  8:48   ` Andre Noll
2017-01-19 12:22     ` Jan Wiele
2017-01-19 13:42       ` Kent Overstreet
2017-01-19 14:06         ` Jan Wiele [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=2468407.km8j8RHp0H@j-t460p \
    --to=jan@wiele.org \
    --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