From: Dave Chinner <david@fromorbit.com>
To: Mark Goodwin <markgw@sgi.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: deadlocked xfs
Date: Fri, 11 Jul 2008 13:22:58 +1000 [thread overview]
Message-ID: <20080711032258.GB11558@disturbed> (raw)
In-Reply-To: <4876C9EB.7060601@sgi.com>
On Fri, Jul 11, 2008 at 12:48:11PM +1000, Mark Goodwin wrote:
> Thanks for the report Eric. This looks very similar to a
> deadlock Lachlan recently hit in the patch for
> "Use atomics for iclog reference counting"
> http://oss.sgi.com/archives/xfs/2008-02/msg00130.html
>
> It seems this patch can cause deadlocks under heavy log traffic.
> I don't think anyone has a fix yet ... Lachlan is out this week,
> but Tim can follow-up here ...
Nice to know - why didn't anyone email me or report this to the
list when the bug was first found? I mean, I wrote that code, I know
what it is supposed to be doing and as a result should be able
help find and fix the bug. Can you please post what details you have
about the problem (test case, stack traces, debugging info, etc)
so I can try to find the problem.
This is a regression that is in the mainline kernel that is due to
be released probably in the next couple of days. Having a little
bit of time to try and find the bug would have been nice...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-07-11 3:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 2:33 deadlocked xfs Eric Sandeen
2008-07-11 2:48 ` Mark Goodwin
2008-07-11 2:56 ` Eric Sandeen
2008-07-11 3:21 ` Timothy Shimmin
2008-07-11 4:04 ` Dave Chinner
2008-07-11 4:10 ` Eric Sandeen
2008-07-11 4:13 ` Timothy Shimmin
2008-07-11 4:18 ` Eric Sandeen
2008-07-11 4:26 ` Eric Sandeen
2008-07-11 4:27 ` Dave Chinner
2008-07-11 4:17 ` Christoph Hellwig
2008-07-11 4:44 ` Timothy Shimmin
2008-07-11 3:22 ` Dave Chinner [this message]
2008-07-11 3:50 ` Mark Goodwin
2008-07-11 4:02 ` Eric Sandeen
2008-07-11 4:05 ` Dave Chinner
2008-07-11 4:08 ` Timothy Shimmin
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=20080711032258.GB11558@disturbed \
--to=david@fromorbit.com \
--cc=markgw@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.