From: Jeff Moyer <jmoyer@redhat.com>
To: Torsten Hilbrich <torsten.hilbrich@secunet.com>
Cc: linux-ext4@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jens Axboe <jaxboe@fusionio.com>, Nick Piggin <npiggin@kernel.dk>
Subject: Re: Kernel 3.3.8 breaks accidental ext3 mount of extended partition
Date: Tue, 19 Jun 2012 13:43:26 -0400 [thread overview]
Message-ID: <x49ehpbjiyp.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4FE0155A.6010404@secunet.com> (Torsten Hilbrich's message of "Tue, 19 Jun 2012 07:59:54 +0200")
Torsten Hilbrich <torsten.hilbrich@secunet.com> writes:
> The system where I reproduced the problem upstream is an amd64 based
> ubuntu 12.04 installation. I used both v3.3.8 and v3.4 for reproducing.
>
> The partition layout is the following:
>
> ======================================================================
>
> Disk /dev/sda: 120.0 GB, 120034123776 bytes
> 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x1669c708
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 63 86285114 43142526 83 Linux
> /dev/sda2 216797175 234436544 8819685 82 Linux swap / Solaris
> /dev/sda3 86285115 87088364 401625 83 Linux
> /dev/sda4 87088426 216797174 64854374+ 5 Extended
> /dev/sda5 87088428 91104614 2008093+ 83 Linux
> /dev/sda6 91104678 216797174 62846248+ 8e Linux LVM
>
> Partition table entries are not in disk order
OK, got it to reproduce, thanks for the info. The attached patch fixed
the problem for me.
Note, though, that the patch doesn't make sense to me. blkdev_max_block
returns i_size_read(blkdev_inode) >> block_size. This should be the
*size* of the block device, not the max block. The code in
fs/block_device.c uses the return value in two different ways!
static int
blkdev_get_block(struct inode *inode, sector_t iblock,
struct buffer_head *bh, int create)
{
if (iblock >= blkdev_max_block(I_BDEV(inode))) {
Here, the return value from blkdev_max_block is interpreted as the size
of the device, so actually max_block + 1.
static int
blkdev_get_blocks(struct inode *inode, sector_t iblock,
struct buffer_head *bh, int create)
{
sector_t end_block = blkdev_max_block(I_BDEV(inode));
unsigned long max_blocks = bh->b_size >> inode->i_blkbits;
if ((iblock + max_blocks) > end_block) {
Here, the return value is treated as the maximum addressable block
number. Given the fact that I had to modify init_page_buffers to treat
the return value from blkdev_max_block as the maximum addressable block,
I clearly have something wrong with my logic. Nick, Jens, care to set
my head straight?
Cheers,
Jeff
diff --git a/fs/buffer.c b/fs/buffer.c
index 838a9cf..769b30b 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -930,7 +930,7 @@ init_page_buffers(struct page *page, struct block_device *bdev,
bh->b_blocknr = block;
if (uptodate)
set_buffer_uptodate(bh);
- if (block < end_block)
+ if (block <= end_block)
set_buffer_mapped(bh);
}
block++;
next prev parent reply other threads:[~2012-06-19 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 5:59 Kernel 3.3.8 breaks accidental ext3 mount of extended partition Torsten Hilbrich
2012-06-18 19:03 ` Jeff Moyer
2012-06-19 5:59 ` Torsten Hilbrich
2012-06-19 17:43 ` Jeff Moyer [this message]
2012-06-20 6:14 ` Torsten Hilbrich
2012-06-22 0:12 ` Jan Kara
2012-06-22 12:33 ` Jeff Moyer
2012-06-20 12:18 ` Marcos Mello
2012-06-25 11:34 ` Richard W.M. Jones
2012-06-25 16:38 ` Jeff Moyer
2012-06-25 16:58 ` Richard W.M. Jones
2012-06-25 19:32 ` Richard W.M. Jones
2012-06-25 20:04 ` Jeff Moyer
2012-06-26 6:07 ` Torsten Hilbrich
2012-06-26 13:02 ` Jeff Moyer
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=x49ehpbjiyp.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=jaxboe@fusionio.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=torsten.hilbrich@secunet.com \
/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;
as well as URLs for NNTP newsgroup(s).