From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: XFS regression: Oops in xfs_buf_do_callbacks on xfstest 137
Date: Fri, 17 Aug 2012 13:15:43 -0500 [thread overview]
Message-ID: <502E8A4F.9050105@sandeen.net> (raw)
In-Reply-To: <20120817180254.GA15382@infradead.org>
On 8/17/12 1:02 PM, Christoph Hellwig wrote:
> I'd be this is my new code added to xfs_buf_item_unpin, but I don't
> quite understand why. It's been a long time since I wrote that code,
> but I had to add that code to make sure we clear all buffers during
> a forced shutdown. Can you test if things go away if you just remove it
> (even if causes other hangs?)
It does go away AFAIK, since the bisect found it.
Sadly it's been on the back burner for me, under other deadline pressure.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-08-17 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 17:44 XFS regression: Oops in xfs_buf_do_callbacks on xfstest 137 Eric Sandeen
2012-08-17 18:02 ` Christoph Hellwig
2012-08-17 18:15 ` Eric Sandeen [this message]
2012-09-03 0:45 ` Raghavendra D Prabhu
2012-09-03 3:05 ` Raghavendra D Prabhu
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=502E8A4F.9050105@sandeen.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox