9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] the futility of QTMOUNT
Date: Wed,  8 Dec 2010 08:16:50 -0500	[thread overview]
Message-ID: <066486e67299fd5a3f2605c8df948616@plug.quanstro.net> (raw)

i've been experimenting a bit with reexporting
namespaces that have remote elements.  sometimes
the remote machine goes away.  unfortunately
when this happens, the first process to wander
into the missing mount hangs up everything.  it
appears that exportfs defends against this; it
is designed to fork when it detects it is traversing
a mount point (exportsrv.c:652).  this test always
fails because QTMOUNT is never set.  it appears that this
bit is always clobbered when being passed up to
user space.  in tracking that down, i noticed that
fixmount traverses the mount point anyway, so
QTMOUNT, even if set, would be seen too late.

so should QTMOUNT be removed, or have i
missed something?

- erik



             reply	other threads:[~2010-12-08 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 13:16 erik quanstrom [this message]
2010-12-08 16:26 ` Charles Forsyth
2010-12-08 16:24   ` erik quanstrom
2010-12-08 17:19     ` Charles Forsyth

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=066486e67299fd5a3f2605c8df948616@plug.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).