From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] fd and /srv filesystem
Date: Wed, 4 Oct 2023 14:20:25 +0200 [thread overview]
Message-ID: <CAFSF3XNMyPj+cY8=_-vpcgtFHVoBERNxiJiFzqo_nLvU8y3KKg@mail.gmail.com> (raw)
In-Reply-To: <CAOk9ws3XmDacBCrsJajY1S3GumOPEM48gwQnkxg+1FD-Etwf=Q@mail.gmail.com>
file descriptors describe to the kernel which of the files you
previously open()'ed (a syscall) you want to operator on.
it's not about security: if you want to operate on a file that another
process might have opened before, you have to be careful that the
other process isn't writing to the same location in the file at the
same time. the kernel also keeps offsets for you.
if you share FDs between multiple processes you might want some
synchronisation like locking.
On 10/4/23, Chris McGee <newton688@gmail.com> wrote:
> Hi All,
>
> I was thinking about file descriptors in the context of Plan 9. On Unix an
> fd is generally only usable by the current process, and child ones through
> a fork with some special incantation if one wants to communicate one over a
> domain socket. This is possibly for security reasons, avoiding other users'
> processes from trying to guess the fd of a critical file.
>
> It's common practice in Plan 9 to post an fd (sometimes via a pipe) from
> one process to the /srv filesystem so that others can discover it and open
> a comms channel. Does the kernel transform the fd into something when
> posted to /srv so that it can be consumed by any other process in the
> system?
>
> Thanks,
> Chris
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tfaa2554a9b74c479-Md097c18fd19852d1e89a068c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-10-04 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 10:29 Chris McGee
2023-10-04 12:20 ` hiro [this message]
2023-10-04 12:25 ` hiro
2023-10-04 16:06 ` ori
2023-10-04 23:42 ` Chris McGee
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='CAFSF3XNMyPj+cY8=_-vpcgtFHVoBERNxiJiFzqo_nLvU8y3KKg@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).