From: Kris Kennaway <kris@obsecurity.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Kris Kennaway <kris@freebsd.org>, linux-kernel@vger.kernel.org
Subject: Re: NFS Locking violates protocol spec (incompatible with FreeBSD)
Date: Thu, 6 Nov 2003 20:53:47 -0800 [thread overview]
Message-ID: <20031107045346.GA4583@rot13.obsecurity.org> (raw)
In-Reply-To: <shsk76c3hvr.fsf@charged.uio.no>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Thu, Nov 06, 2003 at 11:46:48PM -0500, Trond Myklebust wrote:
> >>>>> " " == Kris Kennaway <kris@freebsd.org> writes:
>
>
> > contains more details about this problem, including a
> > workaround for FreeBSD to limit the cookie size to 8 bytes.
> > Obviously, it would be better for this bug to be fixed in
> > Linux, since Linux is non-conformant to the protocol.
>
> Yes. I saw a mail with a justification for why you want to be able to
> wait on > 2^64 outstanding lock requests to a single lockd server, and
> was highly amused.
> I'm still hoping the person who decided that he needed 1024 byte
> long cookies will own up some day. OTOH, he might still be busy
> testing his locking code for cookie wraparound...
>
>
> Anyhow, a patch exists (written by Greg Banks), and can be found as
>
> http://www.fys.uio.no/~trondmy/src/Linux-2.4.x/2.4.23-pre9/linux-2.4.23-01-fix_osx.dif
>
>
> No. It does not extend the cookie size to 1k...
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?
Kris
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2003-11-07 4:53 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 [this message]
2003-11-07 6:13 ` Trond Myklebust
2003-11-07 6:32 ` Kris Kennaway
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=20031107045346.GA4583@rot13.obsecurity.org \
--to=kris@obsecurity.org \
--cc=kris@freebsd.org \
--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 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.