linux-kernel - Re: Why aren't partitions limited to fit within the device?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Oct 2006 08:27:15 +0300
From:	Ville Herva <vherva@...nova.fi>
To:	Neil Brown <neilb@...e.de>
Cc:	linux-kernel@...r.kernel.org, aeb@....nl,
	Jens Axboe <jens.axboe@...cle.com>
Subject: Re: Why aren't partitions limited to fit within the device?

On Mon, Oct 16, 2006 at 09:50:15AM +1000, you [Neil Brown] wrote:
> On Sunday October 15, vherva@...nova.fi wrote:
> > On Fri, Oct 13, 2006 at 09:50:49AM +1000, you [Neil Brown] wrote:
> > > 
> > > Hi,
> > >  I was looking into an issue that someone was having with raid5.
> > > They made an md/raid5 out of 5 whole devices and by luck the data
> > > that was written to the first block of the 5th device looked
> > > slightly like a partition table.  fdisk output below for the curious.
> > > However some partitions were beyond the end of the device.
> > 
> > That reminds me of an old long-standing mystery I had with a machine that
> > had a RAID-5 of three whole devices. 
> > 
> > I wonder if there's ever a change the kernel partition detection code could
> > _write_ on the disk, even when there's really no partition table?
> 
> No, kernel partition detection never writes.

Well yeah, that sounded very improbable to begin with. But then again, there
were very few things that could've done it apart from kernel early boot/late
shutdown code, bios and cosmic radiation. 
 
> I can't imagine what could have been causing your very-interesting
> corruption.  However as it was only demonstrated on old code and
> cannot be explored further, I suspect we just have to forget it and
> move one :-(

Yes, that's certainly the most sensible thing to do.

Although it did happen with both 2.2 and 2.4 (never tried 2.6
unfortunately), but only on a single box, and I never heard of anybody else
seeing anything similar, so it can't be a wide spread problem even it still
were present.

Thanks for the reply.



-- v -- 

v@....fi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/