From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <zwisler@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfs: fix realtime device assert failures
Date: Sat, 6 Feb 2016 09:35:19 +1100 [thread overview]
Message-ID: <20160205223519.GM459@dastard> (raw)
In-Reply-To: <CAOxpaSVs=DmbjsBH68wwQVZeP4dm4PkfA3=jQF3LhR_kgp2tFQ@mail.gmail.com>
On Thu, Feb 04, 2016 at 02:22:17PM -0700, Ross Zwisler wrote:
> This series solves the assert and the follow-up XFS warning for me.
>
> Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
>
> The lockdep splat is still there, but I assume you know that.
Mostly I don't care about lockdep splats because experience tells me
they are wild goose chases that end with us jumping through ever
more complex flaming hoops to annotate the special corner case
lockdep has falsely triggered on.
I also don't have time to care about lockdep right now, so I'm
ignoring it until it manifests itself as a real deadlock.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-02-05 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 0:39 [PATCH 0/3] xfs: fix realtime device assert failures Dave Chinner
2016-02-02 0:39 ` [PATCH 1/3] xfs: lock rt summary inode on allocation Dave Chinner
2016-02-02 1:26 ` Eric Sandeen
2016-02-02 0:39 ` [PATCH 2/3] xfs: RT bitmap and summary buffers are not typed Dave Chinner
2016-02-02 1:26 ` Eric Sandeen
2016-02-02 0:39 ` [PATCH 3/3] xfs: RT bitmap and summary buffers need verifiers Dave Chinner
2016-02-02 1:25 ` Eric Sandeen
2016-02-04 21:22 ` [PATCH 0/3] xfs: fix realtime device assert failures Ross Zwisler
2016-02-05 22:35 ` Dave Chinner [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=20160205223519.GM459@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=zwisler@gmail.com \
/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