From: Abramo Bagnara <abramo@alsa-project.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: neilb@cse.unsw.edu.au, nfs-devel@linux.kernel.org,
nfs@lists.sourceforge.net
Subject: [PATCH] Bug in NFS
Date: Fri, 13 Jul 2001 08:23:37 +0200 [thread overview]
Message-ID: <3B4E93E9.F6506CC0@alsa-project.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
I have found a bug in NFSv2.
[root@igor /tmp]# mount igor:/u u
[root@igor /tmp]# cd u
[root@igor u]# umask 000
[root@igor u]# ls -l q
ls: q: File o directory inesistente
[root@igor u]# touch q
[root@igor u]# ls -l q
-rw-r--r-- 1 root root 0 lug 13 07:56 q
This seems to be caused by use of unitialized current->fs->umask via
vfs_create called by nfsd_create.
Patch for 2.4.6 follows.
--
Abramo Bagnara mailto:abramo@alsa-project.org
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
ALSA project http://www.alsa-project.org
It sounds good!
[-- Attachment #2: nfs.diff --]
[-- Type: text/plain, Size: 282 bytes --]
--- linux-2.4/fs/nfsd/auth.c.~1~ Mon Jul 24 08:04:10 2000
+++ linux-2.4/fs/nfsd/auth.c Fri Jul 13 08:00:10 2001
@@ -34,6 +34,7 @@
cred->cr_groups[i] = exp->ex_anon_gid;
}
+ current->fs->umask = 0;
if (cred->cr_uid != (uid_t) -1)
current->fsuid = cred->cr_uid;
else
next reply other threads:[~2001-07-13 6:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 6:23 Abramo Bagnara [this message]
2001-07-13 9:27 ` [NFS] [PATCH] Bug in NFS Neil Brown
2001-07-13 11:30 ` Abramo Bagnara
2001-07-13 12:03 ` [NFS] [PATCH] Bug in NFS - should umask be allowed to set umask??? Neil Brown
2001-07-13 12:12 ` Alan Cox
2001-07-13 13:30 ` Trond Myklebust
2001-07-13 22:47 ` [NFS] [PATCH] Bug in NFS - should init " Neil Brown
2001-07-14 2:03 ` Linus Torvalds
2001-07-14 4:49 ` Neil Brown
2001-07-14 5:33 ` Alexander Viro
2001-07-14 10:53 ` Neil Brown
2001-07-14 12:28 ` Alexander Viro
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=3B4E93E9.F6506CC0@alsa-project.org \
--to=abramo@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs-devel@linux.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