CVS log for src/usr.sbin/puffs/mount_9p/ninepuffs.c

Up to [cvs.NetBSD.org] / src / usr.sbin / puffs / mount_9p

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

mount_9p: don't cache path names by default

Caching path names doesn't handle file changes by host, which is
not expected for normal usages.  So turn it off by default.

Instead, -C option is added to turn it on.

Patch from k-goda@IIJ with my tweaks

Support optional square brackets around the host name.

The brackets are required when using numeric IPv6 addresses as they
contain colons as part of their syntax.  We do not enforce that the
thing in the brackets is a numeric IPv6 address - this matches scp
syntax and behavior.

Remove -46 from the -c usage.  While here, sync usage with man page
(s/devfile/device).

Add -46 to usage.

Support IPv6.

Use getaddrinfo(3).  Add -4 and -6 command line options.  Obey USE_INET6.

Initialize puffs9p::server (though it's not used anywhere).

Fix vio9p device name in a comment.

Mostly merge changes from HEAD upto 20200411

mount_9p: enable to communicate with vio9p via its character device file

With this feature, we can mount an exported filesystem by a VM host via
virtio-9p.

Sync with HEAD

mount_9p: add missing -u option to the help message

mount_9p: add initial support for 9P2000.u

The implementation enables to work with a server talking 9P2000.u.  However, it
doesn't use the extended fields yet; it just ignores those of received messages
and sets "please ignore" values to those of sending messages such as zero-length
strings and maximum unsigned values.

The feature is enabled by the -u option.

Use __dead

sync with HEAD

Sort options.

use puffs_daemon() instead of daemon()

sync with HEAD

Open the kernel descriptor as part of mount(), not init().  Then
it doesn't matter if someone fork()s or does other tricks between
init() and mount() (and besides, now it's where it logically should be).

Actually, daemonize the file servers before mounting.  I might require
at some point that the local protocol handler does not change after
the file system has been mounted.

Pull the daemonizing code out of the library mainloop into the file
servers.  Calling daemon() (i.e. fork()ing) inside a library can
cause nice surprises for e.g. threaded programs.  As discussed with
Greg Oster & others.

update usage to match reality.  caught by jmcneill

Adapt to new puffs_framev_init() signature - gotfb.

* add mntfromname parameter to puffs_init()
* set it in file servers

support standard user@host:path mount argument

Accept user as a flag.  This way the usage is fstab-compliant:
  mount_9p argument mountpoint

adapt to puffs_framebuf changes

support reclaim.  set noref setback when removing a node to prompt
immediate reclaim.

reflect changes in fs mount: use puffs_mount() instead of
puffs_domount() & puffs_start()

adapt to "step 3" of puffs_framebuf changes

use puffs_mainloop(); puffs_framebuf_eventloop() is a goner

adapt to puffs_framebuf changes

Use inactive-on-demand, set inactive request in open() to close
file handles when last reference is removed from the kernel.

Close file handles in inactive instead of close - a memory mapping
may still be active after a vnode is closed

adapt to puffs_framebuf_eventloop signature change

Adapt to use puffs_framebuf.  This gets rid of most of the duplicated
code between mount_psshfs and mount_9p and clarifies the code
structure.

For consistency destroy kernel request putbuffers also when
escaping event loop (the process is going to exit anyway, but ...)

Alter the strategy for reading/writing a bit.  First of all, use
PUFFS_KFLAG_WTCACHE.  Second, create separate fids for reading and
writing.  If opening for read, open a read-only fid and for write
a write-only fid; use these for reading and writing.  When the
open-count for a node drops to zero, clunk both.  This avoids hitting
the fid limit when accessing large directory hierarchies.

Two problems remain:
* does not take credentials into account, although we can only mount
  the remote 9P file server with one set of credentials, so not a
  huge worry
* doesn't work for the open/mmap/close/access_memory_window case, but
  that will require some further kernel changes

mount_9p: mount a file server using the Plan9 file sharing protocol

Works, but lots of little things to nibble on:
* fix permissions to work better
* limit the amount of open files required
* do constant folding with psshfs code
* support authentication
etcetc.