Bug 224966 - gbde: should append /bde to the underlying provider's physical path
Summary: gbde: should append /bde to the underlying provider's physical path
Status: Closed Works As Intended
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: Alan Somers
URL:
Keywords:
Depends on:
Blocks: 224963
  Show dependency tree / graph
 
Reported: 2018-01-07 03:41 UTC by Alan Somers
Modified: 2018-03-10 02:02 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 Alan Somers freebsd_committer freebsd_triage 2018-01-07 03:41:45 UTC 
A gbde device's physical path should be the underlying provider's with "/bde" appended, if the underlying provider has a non-null physical path itself.
Comment 1 Alan Somers freebsd_committer freebsd_triage 2018-03-10 02:02:27 UTC 
Turns out this isn't as important as I thought.  gbde(8) currently doesn't even support BIO_GETATTR.  That means that zfsd will never use a gbde device for a physical path replacement, which means that zfsd will never replace a ZFS disk with the bare drive when it should be using the .bde version.

Since there's no risk of mishandling encrypted information, and I don't want to add features to the obsolete GEOM transform, I'm going to close the bug.