linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dave@jikos.cz>
To: Itaru Kitayama <kitayama@cl.bb4u.ne.jp>
Cc: dave@jikos.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: shrink_delalloc check bdi write congested
Date: Mon, 1 Oct 2012 02:10:42 +0200	[thread overview]
Message-ID: <20121001001042.GS14582@twin.jikos.cz> (raw)
In-Reply-To: <CANW9uyvdTthEvEwEDJeVRFKNm+3OF+cUS8Y22fmvKokL-Je4-w@mail.gmail.com>

On Mon, Oct 01, 2012 at 08:55:28AM +0900, Itaru Kitayama wrote:
> Thank you for your comments. I wanted to fix a lockdep warning on a
> possible deadlock
> case encountered during the xfstests with a scratch space almost full.

This is the known cleaner/writeback deadlock and avoiding writeback
under device congestion may avoid it, but not in all cases and we want
to fix it properly (Miao sent the patches, but they're not merged so
far).

> You are right I encountered the worst scenario you described below, I
> drop this patch and
> I'll look at btrfs_congested_fn more to examine the mechanisms
> implemented there are
> working as expected.

I'm not sure what you want to achieve with the congestion checks (other
than avoid the cleaner deadlock).

david

      reply	other threads:[~2012-10-01  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-29 13:20 [PATCH] Btrfs: shrink_delalloc check bdi write congested Itaru Kitayama
2012-09-29 16:21 ` David Sterba
2012-09-30  1:28   ` Itaru Kitayama
2012-09-30  2:11     ` Itaru Kitayama
2012-09-30 22:29       ` David Sterba
2012-09-30 23:55         ` Itaru Kitayama
2012-10-01  0:10           ` David Sterba [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=20121001001042.GS14582@twin.jikos.cz \
    --to=dave@jikos.cz \
    --cc=kitayama@cl.bb4u.ne.jp \
    --cc=linux-btrfs@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).