From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p acme freezes when ctrl-f inside its mounted directory
Date: Wed, 5 Aug 2009 09:48:27 +0200 [thread overview]
Message-ID: <a560a5d00908050048s56c093ffxd079d89251eb5869@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0908041649i3db05d79md93f0e46a57138ed@mail.gmail.com>
2009/8/5 Russ Cox <rsc@swtch.com>:
> On Tue, Aug 4, 2009 at 10:33 AM, Rudolf Sykora<rudolf.sykora@gmail.com> wrote:
>> I noticed that when running acme in plan9port and having its
>> directories mounted say on /mnt/acme, then if I try from within a win
>> window in the acme to auto-complete a directory name---I am in /mnt, I
>> type 'a' and hit the 'insert' key or ctrl-f, or I am anywhere inside
>> the acme filesystem---the program freezes (though, if I write it
>> myself, I can cd to the acme directory).
>
> The problem is that acme is basically a single
> operating system thread, and that operating system
> thread is trying to look in /mnt/acme. To serve that
> request, the kernel has posted a FUSE message to
> acme to handle, which acme will get around to just as
> soon as the system call in /mnt/acme finishes.
> Deadlock.
>
> This is not a problem on Plan 9 because acme does
> not put itself in its own name space. On Linux, where
> there is just one big name space, more care is necessary
> (and not implemented).
>
> Russ
>
>
Thanks for the explanation!
R
prev parent reply other threads:[~2009-08-05 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 17:33 Rudolf Sykora
2009-08-04 23:49 ` Russ Cox
2009-08-05 7:48 ` Rudolf Sykora [this message]
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=a560a5d00908050048s56c093ffxd079d89251eb5869@mail.gmail.com \
--to=rudolf.sykora@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).