Bug 120044 - [msdosfs] [geom] incorrect MSDOSFS label fries administrative access to GEOM
Summary: [msdosfs] [geom] incorrect MSDOSFS label fries administrative access to GEOM
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 6.3-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-geom (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-27 15:40 UTC by Bernard Steiner
Modified: 2009-08-12 22:00 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bernard Steiner 2008-01-27 15:40:11 UTC 
An unexpected msdosfs label can fry GEOM.
I have an old memory stick which happens to have (had ;-) a non-standard
MSDOSFS label on it, viz:

Jan 26 11:28:34 grimma kernel: umass0: vendor 0x0c76 product 0x0005, rev 1.10/1.00, addr 3
Jan 26 11:28:34 grimma kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Jan 26 11:28:34 grimma kernel: da0: (JetFlash Transcend 1.00) Removable Direct Access SCSI-2 device 
Jan 26 11:28:34 grimma kernel: da0: 1.000MB/s transfers
Jan 26 11:28:34 grimma kernel: da0: 61MB (126600 512 byte sectors: 64H 32S/T 61C)
Jan 26 11:28:35 grimma kernel: GEOM_LABEL: Label for provider da0 is msdosfs/(A0)(EA)(FF)(FF)(FF).

(I replaced less-than and greater-than in those lines)

Doing something like "gmirror status" while that memory stick is inserted
yields a nice "Cannot get GEOM tree: Unknown error: -1."  Note that the
operation of the actual gmirror (and glabel, geli) devices is not affected
afaik.

The same stick works perfectly after being re-mlabel-d to a decent name.
Stops working if the label is re-set to those unprintables...

How-To-Repeat: mlabel an msdosfs filesystem to 0xa0 0xea 0xff 0xff 0xff
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2008-01-28 00:24:50 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-geom

Over to maintainer(s).
Comment 2 Jaakko Heinonen 2008-02-04 16:13:51 UTC 
This bug is a duplicate of kern/104389
(http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/104389).
Comment 3 Jilles Tjoelker freebsd_committer freebsd_triage 2009-08-12 22:00:32 UTC 
State Changed
From-To: open->closed

duplicate of kern/104389