From: Romain Francoise <romain@orebokech.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.7-rc8
Date: Mon, 03 Dec 2012 23:20:45 +0100 [thread overview]
Message-ID: <874nk2u69u.fsf@silenus.orebokech.com> (raw)
In-Reply-To: <CA+55aFyFLG+SxRq2=wY=8tyuQzQSHkKxonXwMmCOs=CWyOo=Mg@mail.gmail.com> (Linus Torvalds's message of "Mon, 3 Dec 2012 12:36:26 -0800")
Hi Linus,
Linus Torvalds <torvalds@linux-foundation.org> writes:
> Linus Torvalds (5):
> fs/buffer.c: make block-size be per-page and protected by the page lock
> blockdev: remove bd_block_size_semaphore again
> direct-io: don't read inode->i_blkbits multiple times
> blkdev_max_block: make private to fs/buffer.c
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
Thanks.
next prev parent reply other threads:[~2012-12-03 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 20:36 Linus Torvalds
2012-12-03 20:55 ` Stephen Rothwell
2012-12-03 22:20 ` Romain Francoise [this message]
[not found] ` <CA+8MBbLv9SxeW2sbOoQxeNHbwrpqXnpFjJoHgQAk7VyfbCpn4g@mail.gmail.com>
2012-12-03 22:32 ` Tony Luck
2012-12-03 22:34 ` Linus Torvalds
2012-12-03 22:44 ` Tony Luck
2012-12-03 23:07 ` Linus Torvalds
2012-12-03 23:14 ` Linus Torvalds
2012-12-03 23:40 ` Linus Torvalds
2012-12-04 2:02 ` Linus Torvalds
2012-12-04 7:10 ` Romain Francoise
2012-12-04 18:30 ` Tony Luck
2012-12-03 22:44 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874nk2u69u.fsf@silenus.orebokech.com \
--to=romain@orebokech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome