robin.thoni/ipxe - git rthoni.com

Michael Brown 639632b059 [hyperv] Assume that VMBus xfer page ranges correspond to RNDIS messages The (undocumented) VMBus protocol seems to allow for transfer page-based packets where the data payload is split into an arbitrary set of ranges within the transfer page set. The RNDIS protocol includes a length field within the header of each message, and it is known from observation that multiple RNDIS messages can be concatenated into a single VMBus message. iPXE currently assumes that the transfer page range boundaries are entirely arbitrary, and uses the RNDIS header length to determine the RNDIS message boundaries. Windows Server 2012 R2 generates an RNDIS_INDICATE_STATUS_MSG for an undocumented and unknown status code (0x40020006) with a malformed RNDIS header length: the length does not cover the StatusBuffer portion of the message. This causes iPXE to report a malformed RNDIS message and to discard any further RNDIS messages within the same VMBus message. The Linux Hyper-V driver assumes that the transfer page range boundaries correspond to RNDIS message boundaries, and so does not notice the malformed length field in the RNDIS header. Match the behaviour of the Linux Hyper-V driver: assume that the transfer page range boundaries correspond to the RNDIS message boundaries and ignore the RNDIS header length. This avoids triggering the "malformed packet" error and also avoids unnecessary data copying: since we now have one I/O buffer per RNDIS message, there is no longer any need to use iob_split(). Signed-off-by: Michael Brown <mcb30@ipxe.org>		10 anni fa
contrib	[errdb] Strip platform error code for non-platform-generated errors	12 anni fa
src	[hyperv] Assume that VMBus xfer page ranges correspond to RNDIS messages	10 anni fa
COPYING	Initial revision	20 anni fa
COPYRIGHTS	[build] Rename gPXE to iPXE	15 anni fa
README	[doc] Re-add README file	15 anni fa

iPXE README File

Quick start guide:

   cd src
   make

For any more detailed instructions, see http://ipxe.org