[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] ioemu block device extent checks

Daniel P. Berrange writes ("Re: [Xen-devel] [PATCH] ioemu block device extent 
> I don't think this is correct - it allows a -ve  size / nb_sectors
> value when autoextenable is set, and allows out of bounds reads.

That's fine because it's only called like that as a the parent block
driver.  Perhaps a different name would have been better.

Out of bounds reads have to be permitted because the block size in the
header may remain un-updated, so reads of newly-cloned blocks may

> I sent a patch to qemu-devel yuesterday which also uses the auto-extend
> flag, but has separate checks for read vs writes. When doing a write that
> would extend the device it increases the total_sectors count so that the
> subsequent reads can be validated to be within the written bounds.

Well, that seems like makework to me but fine if upstream accept it.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.