| 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
| ||
|
Message-ID: <17714.51511.845336.721450@cse.unsw.edu.au> Date: Mon, 16 Oct 2006 09:50:15 +1000 From: Neil Brown <neilb@...e.de> To: vherva@...nova.fi 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 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. 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 :-( NeilBrown - 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/
Powered by blists - more mailing lists