| 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: <20080212.152826.243855481.davem@davemloft.net> Date: Tue, 12 Feb 2008 15:28:26 -0800 (PST) From: David Miller <davem@...emloft.net> To: jengelh@...putergmbh.de Cc: chris.mason@...cle.com, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, btrfs-devel@....oracle.com Subject: Re: BTRFS partition usage... From: Jan Engelhardt <jengelh@...putergmbh.de> Date: Tue, 12 Feb 2008 15:00:20 +0100 (CET) > Something looks wrong here. Why would btrfs need to zero at all? So that existing superblocks on the partition won't be interpreted as correct by other filesystems. It's a safety measure many mkfs programs use. > Superblock at 0, and done. Just like xfs. No, we won't do stupid things like that and make an entire cylinder of our disks unusable. See my other reply. -- 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