|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 1/2] xen/xsm: forbid PV guest console reads
On 09/30/2013 02:06 PM, Konrad Rzeszutek Wilk wrote: On Mon, Sep 30, 2013 at 01:29:00PM -0400, Daniel De Graaf wrote:On 09/30/2013 12:10 PM, Jan Beulich wrote:On 30.09.13 at 17:48, Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> wrote:When the hypervisor was compiled in debug mode (with VERBOSE defined), PV guests incorrectly had access to both read and write to the console. Change this to only allow write access; since such writes were limited by log levels in 48d50de8e0, remove the dependency on VERBOSE completely.I disagree, and iirc I disagreed already when you tried to drop the dependency on VERBOSE with that earlier patch.Reported-by: Jan Beulich <JBeulich@xxxxxxxx> Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> --- Alternatively, if controlling writes with VERBOSE is still desired, the ifdef VERBOSE can be retained surrounding the if() with the following commit message:That's what I'd want to see go in. JanThis patch retains the existing behavior where only HVM guests can use the console for output, and only via the 0xE9 I/O port. With Konrad's Linux patch, this means that xen_raw_console_write in non-dom0 will produce output only on Xen <= 4.3 (which returns -ENOSYS rather than -EPERM, as this code does). All of your bullets are true if the hypervisor is compiled with VERBOSE (which is enabled if debug=y). Otherwise, only priv guests will be able to use console_write (and it won't matter if they are PV or HVM). Either way, only priv guests will be able to use console_read - which is the only thing the below patch actually changes.
-- Daniel De Graaf National Security Agency _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |