On Mon, Jun 23, 2014 at 02:57:36PM +0200, Markus Armbruster wrote:
Markus Armbruster arm...@redhat.com writes:
Stefan Hajnoczi stefa...@redhat.com writes:
On Thu, Jun 05, 2014 at 02:15:36PM +0200, Markus Armbruster wrote:
+if (sector total_sectors || nb_sectors total_sectors -
Stefan Hajnoczi stefa...@redhat.com writes:
On Thu, Jun 05, 2014 at 02:15:36PM +0200, Markus Armbruster wrote:
+if (sector total_sectors || nb_sectors total_sectors - sector) {
+return false;
+}
if (sector = total_sectors || ...) {
I suspect reading
Markus Armbruster arm...@redhat.com writes:
Stefan Hajnoczi stefa...@redhat.com writes:
On Thu, Jun 05, 2014 at 02:15:36PM +0200, Markus Armbruster wrote:
+if (sector total_sectors || nb_sectors total_sectors - sector) {
+return false;
+}
if (sector = total_sectors ||
On Thu, Jun 05, 2014 at 02:15:36PM +0200, Markus Armbruster wrote:
+if (sector total_sectors || nb_sectors total_sectors - sector) {
+return false;
+}
if (sector = total_sectors || ...) {
pgpUGK7ac14gb.pgp
Description: PGP signature
The block layer fails such reads and writes just fine. However, they
then get treated like valid operations that fail: the error action
gets executed. Unwanted; reporting the error to the guest is the only
sensible action.
Reject them before passing them to the block layer. This bypasses the
On Thu, 06/05 14:15, Markus Armbruster wrote:
The block layer fails such reads and writes just fine. However, they
then get treated like valid operations that fail: the error action
gets executed. Unwanted; reporting the error to the guest is the only
sensible action.
Reject them before
