public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: trond.myklebust@fys.uio.no,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19 NFS file perms
Date: Sat, 5 Oct 2002 22:36:34 +0200	[thread overview]
Message-ID: <20021005223634.A1205@linux-m68k.org> (raw)
In-Reply-To: <1033834053.4103.4.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Sat, Oct 05, 2002 at 05:07:33PM +0100

On Sat, Oct 05, 2002 at 05:07:33PM +0100, Alan Cox wrote:
> On Sat, 2002-10-05 at 16:50, Trond Myklebust wrote:
> > >>>>> " " == Richard Zidlicky <rz@linux-m68k.org> writes:
> > 
> >      > Hi, on an NFS mounted fs, executing as root I see this:
> > 
> >      > read(4, 0xefffe4cb, 1) = -1 EIO (Input/output error)
> > 
> >      > glibc crashes in fgets because it doesn't expect the problem
> >      > after the file has been successfully opened and mapped.. who is
> >      > at fault here?
> > 
> > The 'soft' mount option perhaps?

no, automount entry is
nfsr            -rw,noatime                     rz:/usr/m68kroot

> If glibc crashes because of an unmap you are I suspect running a gcc 2.3
> snapshot with the buggy and bogus mmap stdio option. If so turn it off
> before it does any more harm.

thanks, this seems to be one part of the solution - it is a glibc snapshot 
from rawhide, somewhat aged in the meantime.
I am still surprised that NFS returns such strange error instead of
EACCESS but that is probably bad interaction with the old NFS server.

Richard
.


      reply	other threads:[~2002-10-05 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 10:21 2.4.19 NFS file perms Richard Zidlicky
2002-10-05 15:50 ` Trond Myklebust
2002-10-05 16:07   ` Alan Cox
2002-10-05 20:36     ` Richard Zidlicky [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=20021005223634.A1205@linux-m68k.org \
    --to=rz@linux-m68k.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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