mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chris Jensen <dr_spirograph@technologist.com>
Cc: NFS maillist <nfs@lists.sourceforge.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] New files on read only NFS mount
Date: Mon, 12 Mar 2001 15:56:20 +0100 (CET)	[thread overview]
Message-ID: <15020.58260.471102.944034@charged.uio.no> (raw)
In-Reply-To: <001601c0ab02$df976860$0100a8c0@chris>
In-Reply-To: <001a01c0aac0$80432260$0100a8c0@chris> <shs8zmbksxo.fsf@charged.uio.no> <001601c0ab02$df976860$0100a8c0@chris>

>>>>> " " == Chris Jensen <christopher.jensen@studentmail.newcastle.edu.au> writes:

    >> Details please, the minimum info required being 'which kernel
    >> is your client running'?
    >>

     > Oh yeah, whoops, sorry The server is a 586 and the client is
     > 686.  They're both using nfs-utils 0.2.1, under linux 2.4.0
     > with NFS v3 enabled, with glibc 2.2.1 The pertinent line in
     > /etc/exports is / 192.168.0.1(rw,no_root_squash)

How does the following patch work out?

Cheers,
  Trond

--- fs/nfs/dir.c.orig	Fri Feb  9 20:29:44 2001
+++ fs/nfs/dir.c	Mon Mar 12 15:54:14 2001
@@ -1097,6 +1097,10 @@
 
 	if (!NFS_PROTO(inode)->access)
 		goto out;
+
+	if (error == -EROFS)
+		goto out;
+
 	/*
 	 * Trust UNIX mode bits except:
 	 *




       reply	other threads:[~2001-03-12 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001601c0ab02$df976860$0100a8c0@chris>
     [not found] ` <001a01c0aac0$80432260$0100a8c0@chris>
     [not found]   ` <shs8zmbksxo.fsf@charged.uio.no>
2001-03-12 14:56     ` Trond Myklebust [this message]
2001-03-15  7:09       ` H . J . Lu

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=15020.58260.471102.944034@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=dr_spirograph@technologist.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®