Summary: | [FR] declare fuse fs_virtualized | ||||||
---|---|---|---|---|---|---|---|
Product: | Sisyphus | Reporter: | Michael Shigorin <mike> | ||||
Component: | kernel-feat-core-openvz | Assignee: | Sergey Vlasov <vsu> | ||||
Status: | CLOSED FIXED | QA Contact: | qa-sisyphus | ||||
Severity: | enhancement | ||||||
Priority: | P2 | CC: | dev, lakostis, sr | ||||
Version: | unstable | ||||||
Hardware: | all | ||||||
OS: | Linux | ||||||
URL: | http://forum.openvz.org/index.php?t=msg&goto=6963&#msg_6963 | ||||||
Attachments: |
|
Description
Michael Shigorin
2006-09-29 14:55:29 MSD
Created attachment 1646 [details]
+ .fs_flags = FS_VIRTUALIZED
a hack
this requires modprobe fuse on HN and /dev/fuse (c 10 229) also being made available to VE (--devnodes fuse:rw), so should be reasonably safe for strangers ACK: the proposed hack is safe enough, since requires explicit granting of permissions to VE. However, the correct way would be to virtualize FUSE correctly... Added this to our TODO list, however this is low prio right now. Thanks, Kirill. Is there an OpenVZ FS virtualization HOWTO anywhere? 2 lakostis: would be nice to have in next ovz kernel, although maybe I'll care myself (need local devices on terminals via ltspfs, hence the trouble). Patch added to kernel-feat-core-openvz-026test019-alt1. Michael, no... not yet :( I think it will be solved by us quite soon, while working on NFS. In general idea is simple: global variables should be analyzed and if its meaning is about some local activity (not global one), then virtualized (i.e. remade to be dynamic. e.g. moved to ve_struct). |