On Mon, Dec 3, 2012 at 2:20 PM, Romain Francoise <rom...@orebokech.com> wrote:
>
> Could these changes be the reason for the following suddenly appearing in
> one of my VMs with rc8 (no such messages with rc7)? Pretty standard virtio
> setup in KVM.
>
> [ 11.832295] attempt to access beyond end of device
> [ 11.832298] vda1: rw=0, want=4192904, limit=4192902
> [ 11.832299] Buffer I/O error on device vda1, logical block 524112
> [ 11.832394] attempt to access beyond end of device
> [ 11.832395] vda1: rw=0, want=4192904, limit=4192902
> [ 11.832396] Buffer I/O error on device vda1, logical block 524112
Yup.
I'm currently debating whether I should just remove the printk (for
3.8) or actually do the iovec truncation by hand. The "remove the
printk" is a bit cheesy, but I suspect it's the simpler/safer
alternative.
Just for info, can you add a "WARN_ON_ONCE()" to handle_bad_sector()
just so that I see which particular path your kvm load triggers.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
