From: Kris Kennaway <kris@obsecurity.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Kris Kennaway <kris@obsecurity.org>,
linux-kernel@vger.kernel.org,
Jonathan Lennox <lennox@cs.columbia.edu>,
Dan Nelson <dnelson@allantgroup.com>
Subject: Re: NFS Locking violates protocol spec (incompatible with FreeBSD)
Date: Thu, 6 Nov 2003 22:32:20 -0800 [thread overview]
Message-ID: <20031107063220.GA5265@rot13.obsecurity.org> (raw)
In-Reply-To: <16299.14326.407197.204384@charged.uio.no>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
On Fri, Nov 07, 2003 at 01:13:10AM -0500, Trond Myklebust wrote:
> >>>>> " " == Kris Kennaway <kris@obsecurity.org> writes:
>
> > Thanks..obviously we'd like a fix to be committed to Linux so
> > that it interoperates out of the box with FreeBSD. What are
> > the chances of this?
>
> For the moment I'm still waiting for confirmation that this patch does
> actually fix the problem on both FreeBSD and OSX/Panther. Once that is
> done, it's up to Marcelo to tell me when he wants it into 2.4.x. He
> has already announce that he only wants critical bugfixes in 2.4.23,
> though, so I would guess that we will have to wait for 2.4.24.
>
> As for 2.6.x, I expect we will have to wait until the code freeze
> lifts. When it does, I already have a backlog of lockd bugfixes to
> port forward from 2.4.x, so it will make sense to merge it together
> with that.
>
> Then we just have to wait for the distributions to catch up ;-)
Thanks. Unfortunately the Linux server I experience this problem with
is not something I can play with, but I've CC'ed two people who
experience this problem with FreeBSD: perhaps they can test the patch
(http://www.fys.uio.no/~trondmy/src/Linux-2.4.x/2.4.23-pre9/linux-2.4.23-01-fix_osx.dif)
Kris
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
prev parent reply other threads:[~2003-11-07 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 4:10 NFS Locking violates protocol spec (incompatible with FreeBSD) Kris Kennaway
2003-11-07 4:46 ` Trond Myklebust
2003-11-07 4:53 ` Kris Kennaway
2003-11-07 6:13 ` Trond Myklebust
2003-11-07 6:32 ` Kris Kennaway [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=20031107063220.GA5265@rot13.obsecurity.org \
--to=kris@obsecurity.org \
--cc=dnelson@allantgroup.com \
--cc=lennox@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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