public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alan Cox <alan@redhat.com>
Cc: neilb@cse.unsw.edu.au (Neil Brown),
	abramo@alsa-project.org (Abramo Bagnara),
	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: 13 Jul 2001 15:30:21 +0200	[thread overview]
Message-ID: <shsu20hvtw2.fsf@charged.uio.no> (raw)
In-Reply-To: <200107131212.f6DCC0v16274@devserv.devel.redhat.com>
In-Reply-To: Alan Cox's message of "Fri, 13 Jul 2001 08:12:00 -0400 (EDT)"

>>>>> " " == Alan Cox <alan@redhat.com> writes:

    >> 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

Well, you can either use the fs_struct from init, or that of the first
process to call nfsd. I'm not sure if there's any real point in having
a chrooted nfsd, but it's easy to implement.

In either case, the principle is the same: use copy_fs_struct() on
whatever you want to clone, then have all the nfsd daemons and the
lockd daemon attach to the new shared fs_struct when they get set up.
No need to replace daemonize...

Cheers,
  Trond

  reply	other threads:[~2001-07-13 13:31 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
2001-07-13 13:30         ` Trond Myklebust [this message]
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=shsu20hvtw2.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=abramo@alsa-project.org \
    --cc=alan@redhat.com \
    --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