archive mirror
 help / color / mirror / Atom feed
From: Gavin Will <>
Subject: Re: [PATCH] writeback: fix range_cyclic writeback vs writepages deadlock
Date: Tue, 26 Mar 2019 09:33:15 +0000	[thread overview]
Message-ID: <> (raw)


We believe we have seen this deadlock issue on our XFS system and
currently are trying the patch (aware of the disclaimer that it may
not be production ready). However trying to repo this issue is very
hard. I was interested in Dave Chinner saying that he had seen a
repeatable deadlock and hoped that meant that there was either a
process or method that could provoke this situation from happening.
Currently we see this deadlock happen about once every 1-2 months and
hence trying to speed the iteration up.

Gavin Will

             reply	other threads:[~2019-03-26  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26  9:33 Gavin Will [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-05  5:45 [PATCH] writeback: fix range_cyclic writeback vs writepages deadlock Dave Chinner
2018-10-05 19:46 ` Andrew Morton
2018-10-05 23:37   ` Dave Chinner

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \

* 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).