From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Eric Sandeen <sandeen@sandeen.net>
Subject: Re: XFS Lock debugging noise or real problem?
Date: Tue, 12 Aug 2008 15:28:46 -0700 [thread overview]
Message-ID: <48A20E9E.9090100@tlinx.org> (raw)
In-Reply-To: <48A0F9FC.1070805@sandeen.net>
Eric Sandeen wrote:
> ...
Is it also known, (and the same bug) when you get the lock warnings when
doing
"xfs_restore", as well (dio_get_page and xfs_ilock)...
Doesn't give me the warm & fuzzies, but I'm sure you've heard that
sentiment plenty
of times...
The bugs with 'sort', & imap were both with xfs_ilock and
shrink_icache_memory.
I saw another bug (different prog) with those two locks that was said to
be a bug in
XFS by Andrew Morton, but he didn't say if it was the same known
"harmless" "bug" or
if it was more serious.
next prev parent reply other threads:[~2008-08-12 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 19:31 Lock debugging noise or real problem? Linda Walsh
2008-08-11 20:10 ` Eric Sandeen
2008-08-12 2:33 ` Linda Walsh
2008-08-12 2:48 ` Eric Sandeen
2008-08-12 3:35 ` Linda Walsh
2008-08-12 22:28 ` Linda A. Walsh [this message]
2008-08-13 0:58 ` XFS " Dave Chinner
2008-08-13 22:05 ` Linda Walsh
2008-08-14 0:41 ` Dave Chinner
2008-08-14 1:04 ` Linda Walsh
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=48A20E9E.9090100@tlinx.org \
--to=xfs@tlinx.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox