xen: Fix possible user space selector corruption
Subsystems (2)
PATCH 1/1 xen: Fix possible user space selector corruption
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to __USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to __USER_DS and __KERNEL_CSso these selector are not changed.
If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of __USER_DS the userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).
Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
This is quite hard to detect cause after a while these selectors are fixed (__USER_DS seems sticky).
Bisecting the code commit 7076aada1040de4ed79a5977dbabdb5e5ea5e249 appears to be the first one that have this issue.
--- arch/x86/xen/smp.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
arch/x86/xen/smp.c +12 -0
@@ -278,6 +278,18 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Assure we use segments with user level access. +* During switching of task these segments got not reloaded +* so it could happen that userspace tasks get Xen ring1 +* selector causing exit with sysenter failures on next +* userspace memory operation. +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Signature · 1 line
1.7.10.4
Quoted 21 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
Looks okay to me but I don't really understand it...
David
Quoted 21 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
Looks okay to me but I don't really understand it...
David
Quoted 21 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
In terms of the correctness of the fix,
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Quoted 27 lines
--- arch/x86/xen/smp.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)arch/x86/xen/smp.c +12
-0@@ -278,6 +278,18 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Assure we use segments with user level access. +* During switching of task these segments got not reloaded +* so it could happen that userspace tasks get Xen ring1 +* selector causing exit with sysenter failures on next +* userspace memory operation. +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Quoted 30 lines · Andrew Cooper
Quoted 21 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
Quoted 9 lines
In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Suggestion for the comment ??
Frediano
Quoted 28 lines
Quoted 27 lines
--- arch/x86/xen/smp.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)arch/x86/xen/smp.c +12
-0@@ -278,6 +278,18 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Assure we use segments with user level access. +* During switching of task these segments got not reloaded +* so it could happen that userspace tasks get Xen ring1 +* selector causing exit with sysenter failures on next +* userspace memory operation. +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Quoted 26 lines · Frediano Ziglio
Quoted 25 lines · Andrew Cooper
Quoted 24 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>
Should this also go in stable tree?
Quoted 41 lines
Quoted 6 lines
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Suggestion for the comment ??
Frediano
Quoted 28 lines
Quoted 27 lines
--- arch/x86/xen/smp.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)arch/x86/xen/smp.c +12
-0@@ -278,6 +278,18 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Assure we use segments with user level access. +* During switching of task these segments got not reloaded +* so it could happen that userspace tasks get Xen ring1 +* selector causing exit with sysenter failures on next +* userspace memory operation. +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Quoted 4 lines · Konrad Rzeszutek Wilk
Quoted 3 lines · Frediano Ziglio
Quoted 2 lines · Andrew Cooper
Quoted 1 line · Frediano Ziglio
Quoted 8 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>Should this also go in stable tree?
Very much so. The change which exposed it for us was from 3.7 iirc, but I believe it has been a latent bug for as long as the native early boot code uses __USER_DS.
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Suggestion for the comment ??
Frediano
My suggestion was to omit the comment entirely, or simplify it to just:
/* Xen starts us with XEN_FLAT_RING1_DS, but linux code expects __USER_DS */
Anyone who wants the full explanation can read the patch description.
~Andrew
Quoted 4 lines · Konrad Rzeszutek Wilk
Quoted 3 lines · Frediano Ziglio
Quoted 2 lines · Andrew Cooper
Quoted 1 line · Frediano Ziglio
Quoted 8 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>Should this also go in stable tree?
Very much so. The change which exposed it for us was from 3.7 iirc, but I believe it has been a latent bug for as long as the native early boot code uses __USER_DS.
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Suggestion for the comment ??
Frediano
My suggestion was to omit the comment entirely, or simplify it to just:
/* Xen starts us with XEN_FLAT_RING1_DS, but linux code expects __USER_DS */
Anyone who wants the full explanation can read the patch description.
~Andrew
Quoted 23 lines · Andrew Cooper
Quoted 4 lines · Konrad Rzeszutek Wilk
Quoted 3 lines · Frediano Ziglio
Quoted 2 lines · Andrew Cooper
Quoted 1 line · Frediano Ziglio
Quoted 8 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>Should this also go in stable tree?
Very much so. The change which exposed it for us was from 3.7 iirc, but I believe it has been a latent bug for as long as the native early boot code uses
__USER_DS.Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Quoted 5 lines
Quoted 3 lines
Quoted 3 lines
Suggestion for the comment ??
Frediano
My suggestion was to omit the comment entirely, or simplify it to just:
Suggesting comments should be omitted because other code is poorly commented seems odd to me.
Quoted 1 line
/* Xen starts us with
XEN_FLAT_RING1_DS, but linux code expects__USER_DS*/
I do think this comment better summarizes the reason for loading the segment registers so I'd prefer this.
David
PATCH v2 1/1 xen: Fix possible user space selector corruption
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to __USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to __USER_DS and __KERNEL_CSso these selector are not changed.
If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of __USER_DS the userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).
Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
This is quite hard to detect cause after a while these selectors are fixed (__USER_DS seems sticky).
Bisecting the code commit 7076aada1040de4ed79a5977dbabdb5e5ea5e249 appears to be the first one that have this issue.
--- arch/x86/xen/smp.c | 9 +++++++++ 1 file changed, 9 insertions(+)
Just changed comment on source code as suggested by Andrew Cooper.
arch/x86/xen/smp.c +9 -0
@@ -245,6 +245,15 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Xen starts us with XEN_FLAT_RING1_DS, but linux code +* expects __USER_DS +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Signature · 1 line
1.7.10.4
Quoted 20 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
Quoted 28 lines
--- arch/x86/xen/smp.c | 9 +++++++++ 1 file changed, 9 insertions(+)Just changed comment on source code as suggested by Andrew Cooper.
arch/x86/xen/smp.c +9
-0@@ -245,6 +245,15 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Xen starts us with XEN_FLAT_RING1_DS, but linux code +* expects __USER_DS +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Quoted 20 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
Quoted 28 lines
--- arch/x86/xen/smp.c | 9 +++++++++ 1 file changed, 9 insertions(+)Just changed comment on source code as suggested by Andrew Cooper.
arch/x86/xen/smp.c +9
-0@@ -245,6 +245,15 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Xen starts us with XEN_FLAT_RING1_DS, but linux code +* expects __USER_DS +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
PATCH v2 1/1 xen: Fix possible user space selector corruption
In reply to David VrabelDue to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to __USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to __USER_DS and __KERNEL_CSso these selector are not changed.
If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of __USER_DS the userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).
Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
This is quite hard to detect cause after a while these selectors are fixed (__USER_DS seems sticky).
Bisecting the code commit 7076aada1040de4ed79a5977dbabdb5e5ea5e249 appears to be the first one that have this issue.
--- arch/x86/xen/smp.c | 9 +++++++++ 1 file changed, 9 insertions(+)
Just changed comment on source code as suggested by Andrew Cooper.
arch/x86/xen/smp.c +9 -0
@@ -245,6 +245,15 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Xen starts us with XEN_FLAT_RING1_DS, but linux code +* expects __USER_DS +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Signature · 1 line
1.7.10.4
Quoted 23 lines · Andrew Cooper
Quoted 4 lines · Konrad Rzeszutek Wilk
Quoted 3 lines · Frediano Ziglio
Quoted 2 lines · Andrew Cooper
Quoted 1 line · Frediano Ziglio
Quoted 8 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>Should this also go in stable tree?
Very much so. The change which exposed it for us was from 3.7 iirc, but I believe it has been a latent bug for as long as the native early boot code uses
__USER_DS.Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Quoted 5 lines
Quoted 3 lines
Quoted 3 lines
Suggestion for the comment ??
Frediano
My suggestion was to omit the comment entirely, or simplify it to just:
Suggesting comments should be omitted because other code is poorly commented seems odd to me.
Quoted 1 line
/* Xen starts us with
XEN_FLAT_RING1_DS, but linux code expects__USER_DS*/
I do think this comment better summarizes the reason for loading the segment registers so I'd prefer this.
David
Quoted 26 lines · Frediano Ziglio
Quoted 25 lines · Andrew Cooper
Quoted 24 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>
Should this also go in stable tree?
Quoted 41 lines
Quoted 6 lines
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Suggestion for the comment ??
Frediano
Quoted 28 lines
Quoted 27 lines
--- arch/x86/xen/smp.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)arch/x86/xen/smp.c +12
-0@@ -278,6 +278,18 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Assure we use segments with user level access. +* During switching of task these segments got not reloaded +* so it could happen that userspace tasks get Xen ring1 +* selector causing exit with sysenter failures on next +* userspace memory operation. +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Quoted 30 lines · Andrew Cooper
Quoted 21 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
Quoted 9 lines
In terms of the correctness of the fix,
Reviewed-by Andrew Cooper <[email protected]>However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Suggestion for the comment ??
Frediano
Quoted 28 lines
Quoted 27 lines
--- arch/x86/xen/smp.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)arch/x86/xen/smp.c +12
-0@@ -278,6 +278,18 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Assure we use segments with user level access. +* During switching of task these segments got not reloaded +* so it could happen that userspace tasks get Xen ring1 +* selector causing exit with sysenter failures on next +* userspace memory operation. +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }
Quoted 21 lines · Frediano Ziglio
Due to the way kernel is initialized under Xen is possible that the ring1 selector used by the kernel for the boot cpu end up to be copied to userspace leading to segmentation fault in the userspace.
Xen code in the kernel initialize no-boot cpus with correct selectors (ds and es set to
__USER_DS) but the boot one keep the ring1 (passed by Xen). On task context switch (switch_to) we assume that ds, es and cs already point to__USER_DSand__KERNEL_CSsothese selector are not changed.If processor is an Intel that support sysenter instruction sysenter/sysexit is used so ds and es are not restored switching back from kernel to userspace. In the case the selectors point to a ring1 instead of
__USER_DSthe userspace code will crash on first memory access attempt (to be precise Xen on the emulated iret used to do sysexit will detect and set ds and es to zero which lead to GPF anyway).Now if an userspace process call kernel using sysenter and get rescheduled (for me it happen on a specific init calling wait4) could happen that the ring1 selector is set to ds and es.
Quoted 7 lines
This is quite hard to detect cause after a while these selectors are fixed (
__USER_DSseems sticky).Bisecting the code commit
7076aada1040de4ed79a5977dbabdb5e5ea5e249appears to be the first one that have this issue.Signed-off-by Frediano Ziglio <[email protected]>
In terms of the correctness of the fix,
However, I am not sure the comment is necessary. The prevailing style is for no justification of loads of segment selectors on boot, and the comment itself refers simply to an interaction issue of 32bit on Xen when making use of sysenter.
Quoted 27 lines
--- arch/x86/xen/smp.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)arch/x86/xen/smp.c +12
-0@@ -278,6 +278,18 @@ static void __init xen_smp_prepare_boot_cpu(void)old memory can be recycled */ make_lowmem_page_readwrite (xen_initial_gdt); +#ifdef CONFIG_X86_32 +/* +* Assure we use segments with user level access. +* During switching of task these segments got not reloaded +* so it could happen that userspace tasks get Xen ring1 +* selector causing exit with sysenter failures on next +* userspace memory operation. +*/ +loadsegment (ds, __USER_DS); +loadsegment (es, __USER_DS); +#endif +xen_filter_cpu_maps ();xen_setup_vcpu_info_placement (); }