[pve-devel] [PATCH v2 container 1/2] fix #1451: add mountoptions to container config
Oguz Bektas
o.bektas at proxmox.com
Tue May 21 12:50:20 CEST 2019
hi!
>
> and we're sure about allowing all?? also there's no option
> on any FS supported option which can include ';' ?
as discussed offline, i'm sending a proposed whitelist for the options
that we might allow in the backend.
i stick to the fs-independent mountoptions for now. will try to handle
conflicts in the backend, since the default behaviour in mountoptions
is the last one wins in case of conflict.
- noatime
- nodiratime
- relatime
- strictatime
- lazytime (?) (not quite sure, idk how much performance this'd bring)
- nodev
- noexec
- nosuid
- owner (?) (implies nosuid + nodev but idk if there's any point)
- noauto
- noiversion (?) (same with lazytime)
- context, fscontext, defcontext, rootcontext (????)
More information about the pve-devel
mailing list