From: Klaus Strebel <klaus.strebel@gmx.net>
To: linux-kernel@vger.kernel.org
Cc: Eric Sandeen <sandeen@sandeen.net>,
Jesper Juhl <jesper.juhl@gmail.com>, David Chinner <dgc@sgi.com>,
xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
viro@zeniv.linux.org.uk
Subject: Re: 2.6.20.3 - possible recursive locking detected - in XFS
Date: Fri, 27 Apr 2007 09:06:24 +0200 [thread overview]
Message-ID: <4631A0F0.4060308@gmx.net> (raw)
In-Reply-To: <4630DDC2.2040705@sandeen.net>
Eric Sandeen schrieb:
> Jesper Juhl wrote:
>> On 26/04/07, David Chinner <dgc@sgi.com> wrote:
>
>>> Known false positive - XFS doesn't have the annotations needed for
>>> this yet; we've got a patch that will probably make it's way into 6.5.22 that
>>> should fix most of these issues.
>
> wow... 6.5.22.... do we really have to wait that long? :)
Why wait? If i remember right ( it's about 3 years ago that it had to do
with it ), its a quite old patch-version of mother ... IRIX :-)
It's fun to see that your can't hide your roots Dave :-) ...
so now that .21 ( of the Linux 2.6 series ) i wonder, will there be
anybody remembering IRIX 6.5.22 when the Linux kernel reaches to that
version number? Hey Google, suck this message in and help us remember
this question !
Cheers to all friends of Linux und IRIX
Klaus
P.S.: Guess i will have to boot my old Indy at home, arrrggghhh,
clock-chip battery will be empty again ... 'll have to reset the MAC ...
must recover the lost root password ... oh Lord ( no, not you Steve ... )
--
Mit freundlichen Grüssen / best regards
Klaus Strebel, Dipl.-Inform. (FH), mailto:klaus.strebel@gmx.net
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
prev parent reply other threads:[~2007-04-27 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 9:16 2.6.20.3 - possible recursive locking detected - in XFS Jesper Juhl
2007-04-25 23:33 ` David Chinner
2007-04-26 10:17 ` Jesper Juhl
2007-04-26 17:13 ` Eric Sandeen
2007-04-27 7:06 ` Klaus Strebel [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=4631A0F0.4060308@gmx.net \
--to=klaus.strebel@gmx.net \
--cc=dgc@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs-masters@oss.sgi.com \
--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.