linux-ext4 - gdisk-created Bios Boot Partition created with NO fs, reports fs TYPE=ext4. Bug/why?

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-next>] [day] [month] [year] [list]

Message-Id: <1424025536.1061731.227795501.40064DE9@webmail.messagingengine.com>
Date:	Sun, 15 Feb 2015 10:38:56 -0800
From:	grantksupport@...ramail.com
To:	linux-ext4@...r.kernel.org
Subject: gdisk-created Bios Boot Partition created with NO fs,
 reports fs TYPE=ext4.  Bug/why?

I'm not entirely sure this is the right list for this question, but it IS ext4 'involved'.  So ...

I create a GPT Bios Boot Partition on a clean disk

	sgdisk -z /dev/sdc
	sgdisk -o /dev/sdc
	sgdisk -n 1:2048:+1M    -t 1:ef02  -c 1:"BIOS Boot"           /dev/sdc

IIUC, at this point, the partition should exist with NO filesystem.

But, if I check with blkid

	blkid /dev/sdc1
		/dev/sdc1: LABEL="RAID_BOOT" UUID="8a828baa-f315-4456-88d2-ff14849eb705" TYPE="ext4" PARTLABEL="BIOS Boot" PARTUUID="2b3b10b1-a458-481e-872c-bada7d244b13" 

Note that it IDs the filesystem type as

	TYPE="ext4"

Why?

Bios Boot Partition should have NO filesystem.

Is blkid correct?  Is there, or isn't there a fs on that partition?

if there isn't, what's causint the 'false' report?

If there IS, how do I make sure there isn't?

grant

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