linux-kernel - Re: [PATCH 11/11] Unplug emulated disks and nics

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 26 May 2010 13:59:28 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Stefano Stabellini <stefano.stabellini@...citrix.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	Don Dutile <ddutile@...hat.com>
Subject: Re: [PATCH 11/11] Unplug emulated disks and nics

On 05/26/2010 05:27 AM, Stefano Stabellini wrote:
> It is needed for LINUX_VERSION_CODE, see below:
>
>   
>>> +
>>> +#define XEN_IOPORT_MAGIC_VAL 0x49d2
>>> +#define XEN_IOPORT_LINUX_PRODNUM 0xffff
>>> +#define XEN_IOPORT_LINUX_DRVVER  ((LINUX_VERSION_CODE << 8) + 0x0)
>>>       

Ah.  What's that for?  Does qemu change its behaviour depending on the
kernel version?  Ah, something to do with blacklisting.  But is the
Linux kernel version the most useful value here?  Shouldn't there be
some kind of separate version number?  And what's the blacklisting stuff
for anyway?

Wow, this interface is perverse.  It reuses the same IO port but changes
function depending on the size of the IO?  Again, wow.

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/