xen: wrap xenbus on xenfs with COMPAT option
PATCH 1/2 xen: wrap xenbus on xenfs with COMPAT option
Since Xen 4.6.0, using xenbus via xenfs (/proc/xen/xenbus) is deprecated and /dev/xen/xenbus via pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.
--- drivers/xen/Kconfig | 12 ++++++++++++ drivers/xen/xenfs/super.c | 10 ++++++++-- 2 files changed, 20 insertions(+), 2 deletions(-)
drivers/xen/Kconfig +12 -0
@@ -123,6 +123,18 @@ config XEN_COMPAT_XENFS a xen platform. If in doubt, say yes. +config XEN_COMPAT_XENFS_XENBUS + bool "xenbus accessible from xenfs" + depends on XENFS + default y + help + Since Xen 4.6.0, xenstore will prefer to use the /dev/xen/xenbus + device over the "xenbus" interface on the xenfs filesystem. + Selecting this causes the kernel to include the "xenbus" + interface on the xenfs filesystem and you can safely say no for + Xen 4.6.0 and newer. + If in doubt, say yes. + config XEN_SYS_HYPERVISOR bool "Create xen entries under /sys/hypervisor" depends on SYSFS
drivers/xen/xenfs/super.c +8 -2
@@ -45,14 +45,20 @@ static const struct file_operations capabilities_file_ops = {static int xenfs_fill_super (struct super_block *sb,void *data,int silent) {static struct tree_descr xenfs_files[] = { - [2 ] = {"xenbus" , &xen_xenbus_fops,S_IRUSR |S_IWUSR }, + [2 ] = +#ifdef CONFIG_XEN_COMPAT_XENFS_XENBUS + {"xenbus" , &xen_xenbus_fops,S_IRUSR |S_IWUSR }, +#endif {"capabilities" , &capabilities_file_ops,S_IRUGO }, {"privcmd" , &xen_privcmd_fops,S_IRUSR |S_IWUSR }, {"" }, };static struct tree_descr xenfs_init_files[] = { - [2 ] = {"xenbus" , &xen_xenbus_fops,S_IRUSR |S_IWUSR }, + [2 ] = +#ifdef CONFIG_XEN_COMPAT_XENFS_XENBUS + {"xenbus" , &xen_xenbus_fops,S_IRUSR |S_IWUSR }, +#endif {"capabilities" , &capabilities_file_ops,S_IRUGO }, {"privcmd" , &xen_privcmd_fops,S_IRUSR |S_IWUSR }, {"xsd_kva" , &xsd_kva_file_ops,S_IRUSR |S_IWUSR },
Signature · 1 line
2.4.10
PATCH 2/2 xen: wrap privcmd on xenfs with COMPAT option
Since Xen 4.7.0, using privcmd via xenfs (/proc/xen/privcmd) is deprecated and /dev/xen/privcmd via pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.
--- drivers/xen/Kconfig | 12 ++++++++++++ drivers/xen/xenfs/super.c | 4 ++++ 2 files changed, 16 insertions(+)
drivers/xen/Kconfig +12 -0
@@ -135,6 +135,18 @@ config XEN_COMPAT_XENFS_XENBUS Xen 4.6.0 and newer. If in doubt, say yes. +config XEN_COMPAT_XENFS_PRIVCMD + bool "privcmd accessible from xenfs" + depends on XENFS + default y + help + Since Xen 4.7.0, Xen userland will prefer to use the + /dev/xen/privcmd device over the "privcmd" interface on the + xenfs filesystem. Selecting this causes the kernel to include + the "privcmd" interface on the xenfs filesystem and you can + safely say no for Xen 4.7.0 and newer. + If in doubt, say yes. + config XEN_SYS_HYPERVISOR bool "Create xen entries under /sys/hypervisor" depends on SYSFS
drivers/xen/xenfs/super.c +4 -0
@@ -50,7 +50,9 @@ static int xenfs_fill_super(struct super_block *sb, void *data, int silent) { "xenbus", &xen_xenbus_fops, S_IRUSR|S_IWUSR }, #endif { "capabilities", &capabilities_file_ops, S_IRUGO }, +#ifdef CONFIG_XEN_COMPAT_XENFS_PRIVCMD { "privcmd", &xen_privcmd_fops, S_IRUSR|S_IWUSR }, +#endif {""}, };
@@ -60,7 +62,9 @@ static int xenfs_fill_super(struct super_block *sb, void *data, int silent) { "xenbus", &xen_xenbus_fops, S_IRUSR|S_IWUSR }, #endif { "capabilities", &capabilities_file_ops, S_IRUGO }, +#ifdef CONFIG_XEN_COMPAT_XENFS_PRIVCMD { "privcmd", &xen_privcmd_fops, S_IRUSR|S_IWUSR }, +#endif { "xsd_kva", &xsd_kva_file_ops, S_IRUSR|S_IWUSR}, { "xsd_port", &xsd_port_file_ops, S_IRUSR|S_IWUSR}, #ifdef CONFIG_XEN_SYMS
Signature · 1 line
2.4.10
PATCH 2/2 xen: wrap privcmd on xenfs with COMPAT option
In reply to Doug GoldsteinSince Xen 4.7.0, using privcmd via xenfs (/proc/xen/privcmd) is deprecated and /dev/xen/privcmd via pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.
--- drivers/xen/Kconfig | 12 ++++++++++++ drivers/xen/xenfs/super.c | 4 ++++ 2 files changed, 16 insertions(+)
drivers/xen/Kconfig +12 -0
@@ -135,6 +135,18 @@ config XEN_COMPAT_XENFS_XENBUS Xen 4.6.0 and newer. If in doubt, say yes. +config XEN_COMPAT_XENFS_PRIVCMD + bool "privcmd accessible from xenfs" + depends on XENFS + default y + help + Since Xen 4.7.0, Xen userland will prefer to use the + /dev/xen/privcmd device over the "privcmd" interface on the + xenfs filesystem. Selecting this causes the kernel to include + the "privcmd" interface on the xenfs filesystem and you can + safely say no for Xen 4.7.0 and newer. + If in doubt, say yes. + config XEN_SYS_HYPERVISOR bool "Create xen entries under /sys/hypervisor" depends on SYSFS
drivers/xen/xenfs/super.c +4 -0
@@ -50,7 +50,9 @@ static int xenfs_fill_super(struct super_block *sb, void *data, int silent) { "xenbus", &xen_xenbus_fops, S_IRUSR|S_IWUSR }, #endif { "capabilities", &capabilities_file_ops, S_IRUGO }, +#ifdef CONFIG_XEN_COMPAT_XENFS_PRIVCMD { "privcmd", &xen_privcmd_fops, S_IRUSR|S_IWUSR }, +#endif {""}, };
@@ -60,7 +62,9 @@ static int xenfs_fill_super(struct super_block *sb, void *data, int silent) { "xenbus", &xen_xenbus_fops, S_IRUSR|S_IWUSR }, #endif { "capabilities", &capabilities_file_ops, S_IRUGO }, +#ifdef CONFIG_XEN_COMPAT_XENFS_PRIVCMD { "privcmd", &xen_privcmd_fops, S_IRUSR|S_IWUSR }, +#endif { "xsd_kva", &xsd_kva_file_ops, S_IRUSR|S_IWUSR}, { "xsd_port", &xsd_port_file_ops, S_IRUSR|S_IWUSR}, #ifdef CONFIG_XEN_SYMS
Signature · 1 line
2.4.10
Quoted 3 lines · Doug Goldstein
Since Xen 4.6.0, using xenbus via xenfs (
/proc/xen/xenbus) is deprecated and/dev/xen/xenbusvia pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.
I would prefer the /proc/xen/xenbus and /proc/xen/evtchn files to be replaced with symlinks to the corresponding /dev/xen/ devices. Then I see no need to ever remove them, thus avoiding the need for yet another config option.
I did briefly look at this and it seemed possible but didn't get as far as actually trying to change it.
David
Quoted 3 lines · Doug Goldstein
Since Xen 4.6.0, using xenbus via xenfs (
/proc/xen/xenbus) is deprecated and/dev/xen/xenbusvia pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.
I would prefer the /proc/xen/xenbus and /proc/xen/evtchn files to be replaced with symlinks to the corresponding /dev/xen/ devices. Then I see no need to ever remove them, thus avoiding the need for yet another config option.
I did briefly look at this and it seemed possible but didn't get as far as actually trying to change it.
David
Quoted 6 lines · David Vrabel
Quoted 3 lines · Doug Goldstein
Since Xen 4.6.0, using xenbus via xenfs (
/proc/xen/xenbus) is deprecated and/dev/xen/xenbusvia pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.I would prefer the ...
/proc/xen/evtchnfiles to be
I meant /proc/xen/privcmd here.
David
Quoted 6 lines · David Vrabel
Quoted 5 lines · David Vrabel
Quoted 3 lines · Doug Goldstein
Since Xen 4.6.0, using xenbus via xenfs (
/proc/xen/xenbus) is deprecated and/dev/xen/xenbusvia pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.
Quoted 6 lines
Quoted 1 line
I would prefer the ...
/proc/xen/evtchnfiles to beI meant
/proc/xen/privcmdhere.David
I can look into that. I do have a few questions, some of which are out of scope from the original patch.
Would it be preferable to just remove "xenbus" from the xenfs filesystem? Ever since Linux 3.14 even if you are running a version of Xen earlier than 4.6 you will not be able to have a disaggregated xenstore (which is the xenbus consumer) due to the addition of F_ATOMIC_POS.
Is it safe for a kernel virtual filesystem to provide a symlink outside of itself where the destination can't be verified? Its possible this already exists and I just don't know off any cases off the top of my head.
Since the /proc/xen mount point has been marked as COMPAT for nearly 6 years would the eventual goal be to move xenfs to somewhere like /sys/hypervisor given that most of the virtual filesystems are mounted under /sys now days?
Signature · 1 line
Doug Goldstein
Quoted 14 lines · Doug Goldstein
Quoted 6 lines · David Vrabel
Quoted 5 lines · David Vrabel
Quoted 3 lines · Doug Goldstein
Since Xen 4.6.0, using xenbus via xenfs (
/proc/xen/xenbus) is deprecated and/dev/xen/xenbusvia pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.Quoted 6 lines
Quoted 1 line
I would prefer the ...
/proc/xen/evtchnfiles to beI meant
/proc/xen/privcmdhere.David
Quoted 7 lines
I can look into that. I do have a few questions, some of which are out of scope from the original patch.
Would it be preferable to just remove "xenbus" from the xenfs filesystem? Ever since Linux 3.14 even if you are running a version of Xen earlier than 4.6 you will not be able to have a disaggregated xenstore (which is the xenbus consumer) due to the addition of
F_ATOMIC_POS.
If /proc/xen/xenbus is made a symlink then older Xen toolstacks will work again.
Quoted 2 lines
Is it safe for a kernel virtual filesystem to provide a symlink outside of itself where the destination can't be verified?
Yes. The symlink target is just a string containing a path.
Quoted 4 lines
Since the
/proc/xenmount point has been marked as COMPAT for nearly 6 years would the eventual goal be to move xenfs to somewhere like/sys/hypervisorgiven that most of the virtual filesystems are mounted under /sys now days?
No. The information might move to /sys/hypervisor (or elsewhere) but xenfs will always be mounted in /proc/xen (or not mounted at all).
David
Quoted 14 lines · Doug Goldstein
Quoted 6 lines · David Vrabel
Quoted 5 lines · David Vrabel
Quoted 3 lines · Doug Goldstein
Since Xen 4.6.0, using xenbus via xenfs (
/proc/xen/xenbus) is deprecated and/dev/xen/xenbusvia pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.Quoted 6 lines
Quoted 1 line
I would prefer the ...
/proc/xen/evtchnfiles to beI meant
/proc/xen/privcmdhere.David
Quoted 7 lines
I can look into that. I do have a few questions, some of which are out of scope from the original patch.
Would it be preferable to just remove "xenbus" from the xenfs filesystem? Ever since Linux 3.14 even if you are running a version of Xen earlier than 4.6 you will not be able to have a disaggregated xenstore (which is the xenbus consumer) due to the addition of
F_ATOMIC_POS.
If /proc/xen/xenbus is made a symlink then older Xen toolstacks will work again.
Quoted 2 lines
Is it safe for a kernel virtual filesystem to provide a symlink outside of itself where the destination can't be verified?
Yes. The symlink target is just a string containing a path.
Quoted 4 lines
Since the
/proc/xenmount point has been marked as COMPAT for nearly 6 years would the eventual goal be to move xenfs to somewhere like/sys/hypervisorgiven that most of the virtual filesystems are mounted under /sys now days?
No. The information might move to /sys/hypervisor (or elsewhere) but xenfs will always be mounted in /proc/xen (or not mounted at all).
David
Quoted 6 lines · David Vrabel
Quoted 3 lines · Doug Goldstein
Since Xen 4.6.0, using xenbus via xenfs (
/proc/xen/xenbus) is deprecated and/dev/xen/xenbusvia pvops is used instead. This is an effort to eventually drop this interface after a reasonable amount of time.I would prefer the ...
/proc/xen/evtchnfiles to be
I meant /proc/xen/privcmd here.
David