From: maht <mattmobile@proweb.co.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] synthetic filesystems and changing data
Date: Fri, 10 Aug 2007 10:40:33 +0100 [thread overview]
Message-ID: <46BC3291.1080008@proweb.co.uk> (raw)
In-Reply-To: <483d078cf46cca92ce349cf45f0f5fc0@terzarima.net>
And just to elucidate further one frees the data on a clunk.
It could be the source of a DoS if your 9p is public facing.
>> why not just tie the fid to a "file" version. then it would be easy
>> to handle offsets.
>>
>
> that's effectively what i do in similar cases. so does ndb/cs, amongst others.
>
>
>
next prev parent reply other threads:[~2007-08-10 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 1:47 John Marshall
2007-08-10 1:57 ` erik quanstrom
2007-08-10 8:13 ` Charles Forsyth
2007-08-10 9:40 ` maht [this message]
2007-08-10 6:49 ` matt
2007-08-10 12:32 ` John Marshall
2007-08-10 15:13 ` Kris Maglione
2007-08-10 15:47 ` nemo
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=46BC3291.1080008@proweb.co.uk \
--to=mattmobile@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/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).