[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FE16A29.9050508@secunet.com>
Date: Wed, 20 Jun 2012 08:14:01 +0200
From: Torsten Hilbrich <torsten.hilbrich@...unet.com>
To: Jeff Moyer <jmoyer@...hat.com>
CC: linux-ext4@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Jens Axboe <jaxboe@...ionio.com>,
Nick Piggin <npiggin@...nel.dk>
Subject: Re: Kernel 3.3.8 breaks accidental ext3 mount of extended partition
Am 19.06.2012 19:43, schrieb Jeff Moyer:
[...]
> 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++;
I can confirm that this patch fixes the problem for my test case too.
Here is the kernel output when performing the mount operation:
attempt to access beyond end of device
sda4: rw=0, want=4, limit=2
EXT3-fs (sda4): error: unable to read superblock
Torsten
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists