RE: [PATCH 2/2] fs/partition/msdos: Fix unusable extended partition for > 512B sector
From: Daniel Taylor
Date: Thu Mar 11 2010 - 17:07:28 EST
> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@xxxxxxxxx]
> Sent: Thursday, March 11, 2010 1:58 PM
> To: Daniel Taylor
> Cc: OGAWA Hirofumi; Andrew Morton; linux-kernel@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH 2/2] fs/partition/msdos: Fix unusable
> extended partition for > 512B sector
>
> On 03/11/2010 01:25 PM, Daniel Taylor wrote:
> >
> > I have not yet tried booting from one of these disks.
> >
> > They are in USB-attached enclosures,
>
> Right...
>
> > attached well after boot, so the
> > bootloader has never seen them.
>
> Wrong. A lot of BIOSes will attempt to boot from USB
> storage. Worse, a
> fair number of BIOSes will hang during startup if a USB
> storage device
> that confuses them -- even if not the primary boot device.
BIOS failures prior to loading the kernel are not Linux'
responsibility. Confused BIOS will still fail, even if the
patch is not implemented, so how does that effect the
acceptance of a patch that fixes post-boot behavior?
>> They simply refuse to mount to a running
>> Linux system because, when the storage for partition size and start was
>> expanded to 64-bit, no one bothered to fix the intermediate storage in
>> msdos.c, so the kernel cannot locate the start nor figure the size of
>> the partitions.
>>
>> Logically, this patch is not complicated. The data types in msdos.c
>> are flat-out wrong, given that the real stored data is of type sector_t.
>> The intermediate variables should not be u32.
>
> I would consider this a bugfix. As such, it should be pushed outside
> the merge window.
>
> -hpa
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/