From: Gregory Herrero
When filling __xen_guest section of a guest, user may define
HYPERCALL_PAGE earlier than VIRT_BASE in the section leading to an
incorrect hypercall page address since an undefined virt_base could be
used to compute hypercall page address.
If there is no VIRT_BASE entry in
From: Gregory Herrero
When filling __xen_guest section of a guest, user may define
HYPERCALL_PAGE earlier than VIRT_BASE in the section leading to an
incorrect hypercall page address since an undefined virt_base could be
used to compute hypercall page address.
If there is no VIRT_BASE entry in
On Wed, Oct 11, 2017 at 06:40:14AM -0600, Jan Beulich wrote:
> >>> On 11.10.17 at 14:03, wrote:
> > When filling __xen_guest section of a guest, user may define
> > HYPERCALL_PAGE earlier than VIRT_BASE in the section leading to an
> > incorrect hypercall page address since an undefined virt_base
From: Gregory Herrero
When filling __xen_guest section of a guest, user may define
HYPERCALL_PAGE earlier than VIRT_BASE in the section leading to an
incorrect hypercall page address since an undefined virt_base could be
used to compute hypercall page address.
If there is no VIRT_BASE entry in
From: Gregory Herrero
When stop_machine_run() is called with NR_CPUS as last argument,
fn_result member must be filled only if an error happens since it is
shared across all cpus.
Assume CPU1 detects an error and set fn_result to -1, then CPU2 doesn't
detect an error and set fn_result to 0
From: Gregory Herrero
When stop_machine_run() is called with NR_CPUS as last argument,
fn_result member must be filled only if an error happens since it is
shared across all cpus.
Assume CPU1 detects an error and set fn_result to -1, then CPU2 doesn't
detect an error and set fn_result to 0
On Wed, May 31, 2017 at 02:30:29AM -0600, Jan Beulich wrote:
> >>> On 30.05.17 at 18:19, wrote:
> > Since fn_result member is shared across all cpus, it must be filled
> > only if an error happens. Assume CPU1 detects an error and set fn_result
> > to -1, then CPU2 doesn't detect an error and set
From: Gregory Herrero
Since fn_result member is shared across all cpus, it must be filled
only if an error happens. Assume CPU1 detects an error and set fn_result
to -1, then CPU2 doesn't detect an error and set fn_result to 0. The
error detected by CPU1 will be ignored.
Signed-off-by: Gr
