From: Jeff Moyer Subject: Re: Kernel 3.3.8 breaks accidental ext3 mount of extended partition Date: Fri, 22 Jun 2012 08:33:30 -0400 Message-ID: References: <4FDEC3C2.4060909@secunet.com> <4FE0155A.6010404@secunet.com> <20120622001202.GG11645@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Torsten Hilbrich , linux-ext4@vger.kernel.org, LKML , Jens Axboe , Nick Piggin To: Jan Kara Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50066 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932823Ab2FVMdo (ORCPT ); Fri, 22 Jun 2012 08:33:44 -0400 In-Reply-To: <20120622001202.GG11645@quack.suse.cz> (Jan Kara's message of "Fri, 22 Jun 2012 02:12:02 +0200") Sender: linux-ext4-owner@vger.kernel.org List-ID: Jan Kara writes: > I think it can have something to do with the fact that the partition size > is not a multiple of 4k (i.e. expected block size)? Ahh, yes. Except that ext3 sets the blocksize to 1k by default. However, I still can't explain why we don't get an error attempting to access beyond the end of the device. I'll keep digging on that. > BTW: blkdev_max_block() is a terrible name for something that intends to > return size in blocks... Fully agreed here, and I'll fix that up when I get my head completely wrapped around this one. Thanks for taking a look, Jan! -Jeff