Date: Wed, 24 Jan 2001 19:45:28 -0800 From: Guy Harris <gharris@flashcom.net> To: Matthias Andree <matthias.andree@stud.uni-dortmund.de> Cc: Guy Harris <gharris@flashcom.net>, Mike Smith <msmith@freebsd.org>, Matthias Andree <ma@dt.e-technik.uni-dortmund.de>, Linux NFS mailing list <nfs@lists.sourceforge.net>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124194528.B345@quadrajet.flashcom.com> In-Reply-To: <20010125011111.A12526@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Thu, Jan 25, 2001 at 01:11:12AM %2B0100 References: <20010124001701.F344@quadrajet.flashcom.com> <200101241104.f0OB4sS10071@mass.dis.org> <20010124101007.A344@quadrajet.flashcom.com> <20010125011111.A12526@emma1.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 25, 2001 at 01:11:12AM +0100, Matthias Andree wrote: > > 2.4.0, which is definitely not an ancient release, still appears, from > > looking at the code in question, to have that buggy behavior. > > There has been a mail on the Linux-kernel mailing list claiming > otherwise, I haven't tested it. I must've been looking at the wrong source tree or something (either one of the 2.2.x trees, or maybe one of the 2.4.0-testX trees, although I think the tree I had before I grabbed 2.4.0 was 2.4.0-test11, which also has the fix) - 2.4.0 does treat nfserr_rofs the same way it treats nfserr_acces or nfserr_perm, so it shouldn't have the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010124194528.B345>