From: Richard Zidlicky <rz@linux-m68k.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: 2.4.19 NFS file perms
Date: Sat, 5 Oct 2002 12:21:15 +0200 [thread overview]
Message-ID: <20021005122115.A1338@linux-m68k.org> (raw)
Hi,
on an NFS mounted fs, executing as root I see this:
[root@sirizidl nfsr]# ll /nfsr/toplev.fig
-rw------- 1 kernel users 48500 Oct 5 11:42 /nfsr/toplev.fig
[root@sirizidl nfsr]# xfig /nfsr/toplev.fig
[snip]
...
stat64("toplev.fig", {st_mode=S_IFREG|0600, st_size=48500, ...}) = 0
open("toplev.fig", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=48500, ...}) = 0
old_mmap(NULL, 48500, PROT_READ, MAP_PRIVATE, 4, 0) = 0xc0011000
read(4, 0xefffe4cb, 1) = -1 EIO (Input/output error)
_llseek(4, 48500, [48500], SEEK_SET) = 0
--- SIGBUS (Bus 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?
Remote nfs server is an old userspace implementation btw.
Richard
next reply other threads:[~2002-10-05 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 10:21 Richard Zidlicky [this message]
2002-10-05 15:50 ` 2.4.19 NFS file perms Trond Myklebust
2002-10-05 16:07 ` Alan Cox
2002-10-05 20:36 ` Richard Zidlicky
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=20021005122115.A1338@linux-m68k.org \
--to=rz@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox