This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue Apr 23 21:53:34 2024 Received: from entropy.muc.muohio.edu (IDENT:root@entropy.muc.muohio.edu [134.53.213.10]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id OAA22760 for ; Sun, 9 May 1999 14:43:42 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by entropy.muc.muohio.edu (8.8.7/8.8.7) with ESMTP id PAA15632; Sun, 9 May 1999 15:40:28 -0400 Received: by vger.rutgers.edu via listexpand id <156358-17483>; Sun, 9 May 1999 14:45:46 -0400 Received: by vger.rutgers.edu id <156270-17483>; Sun, 9 May 1999 14:45:27 -0400 Received: from heaton.cl.cam.ac.uk ([128.232.32.11]:4248 "EHLO heaton.cl.cam.ac.uk" ident: "exim") by vger.rutgers.edu with ESMTP id <156287-17483>; Sun, 9 May 1999 14:45:19 -0400 Received: from gooch.cl.cam.ac.uk ([128.232.0.109] helo=cl.cam.ac.uk ident=pb) by heaton.cl.cam.ac.uk with esmtp (Exim 2.12 #1) id 10gZE0-000624-00; Sun, 9 May 1999 20:26:56 +0100 X-uri: X-Face: &@N3QE9h|>f`igFCkZ'a1`z=nNLXb}k>H(79G"V?@!&*yn)uhPBctF1vc}LD'{OA%$bs X+l[wN,I^G8kKj2NFxQrr@1C4QBC]hq5-%ZkV,^Zl/qE<0`zCQ1nM+]-N<^WG[H)]?d) A:L9AFgOU[BjbaY)uBAMz}h!fm^O0# To: hjl@lucon.org (H.J. Lu) Cc: nfs-devel@linux.kernel.org (Linux NFS), linux-kernel@vger.rutgers.edu (linux kernel) Subject: Re: Problem with knfsd 1.3. In-Reply-To: Your message of Sun, 09 May 1999 10:57:50 -0700. <19990509175750.A4C1957BB@ocean.lucon.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <5135.926277850.0@cl.cam.ac.uk> Date: Sun, 09 May 1999 20:26:53 +0100 From: Piete Brooks Message-Id: Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5135.926277850.1@cl.cam.ac.uk> > After releasing knfsd 1.3, I found a NFS locking bug. But I haven't > tracked down where the bug is. I export /var/spool/mail. I have > -rw------- 1 hjl mail 115263 May 9 10:49 /var/spool/mail/hjl Sounds to me like the second part of the problem I reported in the last week. See if changing the file to be world readable fixes it ... > My server is running Linux 2.2.7 plus knfsd 1.3 and client is running > 2.2.7 plus knfsd 1.3. I tend to think NFS locking is broken. Agreed -- it's the nlmsvc_ops->fopen call that's the problem ... ------- =_aaaaaaaaaa0 Content-Type: message/rfc822 Content-ID: <5135.926277850.2@cl.cam.ac.uk> Content-Description: forwarded message To: Linux Kernel Subject: Known problems with Linux 2.2.* and knfsd 0.4.22 ? In-reply-to: Your message of Mon, 03 May 1999 21:11:20 -0700. <199905040411.VAA03200@Harpo.ixlabs.com> Date: Tue, 04 May 1999 14:12:12 +0100 From: Piete Brooks Message-Id: Exec summary: Are there known problems with knfsd 0.4.22 quota on truncation ? Also: should locking work on non world readable files ? Fully gory details .... I have knfsd 0.4.22 on Linux 2.2.[0-7], basically for the user land programmes. I find it really hard to keep track of which bits of knfsd are std in the kernel, which bits are "optional" patches to add new features (like NFS V3), which bits are bug fixes, and which bits are required patches. This has resulted in me using out of date (0.4.22 vs 1.2) knfsd user space commands. No problem, except that it appears that if a file is truncated (rather than deleted) over NFS, the amount of space marked as `used' by that user does not go down. Is this a known problem ? Will knfsd 1.2 fix it ? If so, what patches do I need to apply to 2.2.7 ? Also, I find that whereas locking works in general, I have instances when a simple remote perl lock command fails if the file being locked (e.g. a .mail file) isn't world readable :-( It appears that when nlm_lookup_file calls nlmsvc_ops->fopen, current->fsuid is (for *SOME* clients hosts) set to "nobody", rather the actual user, with the result that locking fails. Ideas ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/ ------- =_aaaaaaaaaa0-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/