From: Alan Cox <alan@redhat.com>
To: neilb@cse.unsw.edu.au (Neil Brown)
Cc: abramo@alsa-project.org (Abramo Bagnara),
torvalds@transmeta.com (Linus Torvalds),
linux-kernel@vger.kernel.org (Linux Kernel),
nfs-devel@linux.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] [PATCH] Bug in NFS - should umask be allowed to set umask???
Date: Fri, 13 Jul 2001 08:12:00 -0400 (EDT) [thread overview]
Message-ID: <200107131212.f6DCC0v16274@devserv.devel.redhat.com> (raw)
In-Reply-To: <15182.58236.133661.221154@notabene.cse.unsw.edu.au> from "Neil Brown" at Jul 13, 2001 10:03:08 PM
> 1/ Claim that redhat is broken. Leave them to fix SysVinit.
> 2/ Have nfsd over-write the umask setting that /sbin/init imposed.
> This is effectively what your patch does.
> 3/ Decide that it is inappropriate for nfsd to share the current->fs
> fs_struct with init. Unfortunately this means changing or
> replacing daemonize().
#3 seems right. Of course its not clear whose fs struct should be shared
next prev parent reply other threads:[~2001-07-13 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 6:23 [PATCH] Bug in NFS Abramo Bagnara
2001-07-13 9:27 ` [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 [this message]
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=200107131212.f6DCC0v16274@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=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 \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.