From: erik quanstrom <quanstro@quanstro.net>
To: forsyth@terzarima.net, 9fans@9fans.net
Subject: Re: [9fans] the futility of QTMOUNT
Date: Wed, 8 Dec 2010 11:24:02 -0500 [thread overview]
Message-ID: <5e3c9c7f180af13e74219014e5d078c8@ladd.quanstro.net> (raw)
In-Reply-To: <8f646c8069d0c94b170f73daec7c7a42@terzarima.net>
On Wed Dec 8 11:18:55 EST 2010, forsyth@terzarima.net wrote:
> QTMOUNT allows exportfs to detect an attempt to open a /srv file
> that has been opened and mounted somewhere on the system running exportfs
> (i'll refer to that as the `called system' and the client of exportfs as
> the `calling system').
exportfs never detects this bit being set. i would expect the
type to be 90, not 80 in this example
; mkdir q; mount /srv/boot q; ls -qd q
(0000000000000001 48 80) q
if this isn't when QTMOUNT is set, when would it be set?
i can't find a single file in the system with qid.type&0x10.
- erik
next prev parent reply other threads:[~2010-12-08 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 13:16 erik quanstrom
2010-12-08 16:26 ` Charles Forsyth
2010-12-08 16:24 ` erik quanstrom [this message]
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=5e3c9c7f180af13e74219014e5d078c8@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=forsyth@terzarima.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).