From: Paul Smith <paul@mad-scientist.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux XFS <linux-xfs@oss.sgi.com>, david chinner <dgc@sgi.com>,
linux-kernel@vger.kernel.org,
christoph hellwig <hch@ifradead.org>
Subject: Re: [2.6.27.25] assfail in xfs_attr_quiesce() during umount
Date: Tue, 07 Jul 2009 16:18:43 -0400 [thread overview]
Message-ID: <1246997925.2984.1.camel@psmith-ubeta.netezza.com> (raw)
In-Reply-To: <20090707190643.GA32467@infradead.org>
On Tue, 2009-07-07 at 15:06 -0400, Christoph Hellwig wrote:
> It looks somehwat dangerous for me. For now I would just comment
> out the assert or change it to a WARN_ON as in the newer kernels.
Hah! :-). OK, that works for me.
Thanks Christoph.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-07 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 18:42 [2.6.27.25] assfail in xfs_attr_quiesce() during umount Paul Smith
2009-07-07 19:06 ` Christoph Hellwig
2009-07-07 20:18 ` Paul Smith [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=1246997925.2984.1.camel@psmith-ubeta.netezza.com \
--to=paul@mad-scientist.net \
--cc=dgc@sgi.com \
--cc=hch@ifradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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