Page MenuHomeFreeBSD

Clear G_CF_ORPHAN when attaching.
ClosedPublic

Authored by trasz on Sep 4 2017, 11:08 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Sep 27, 2:34 AM
Unknown Object (File)
Fri, Sep 26, 6:38 AM
Unknown Object (File)
Thu, Sep 25, 1:35 PM
Unknown Object (File)
Sun, Sep 21, 3:24 AM
Unknown Object (File)
Sep 7 2025, 7:54 PM
Unknown Object (File)
Aug 31 2025, 1:11 AM
Unknown Object (File)
Aug 26 2025, 3:51 AM
Unknown Object (File)
Jul 29 2025, 2:38 AM
Subscribers

Details

Summary

Clear G_CF_ORPHAN when attaching. This fixes cases where the same
GEOM consumer can be orphaned, and then reattach to another provider.

From a user point of view, this makes gmountver(4) work again.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I have no specific objections. Probably I was just thinking that consumer should be destroyed and recreated after orphan event happened, but if gmountver does not go it, this indeed may help. I just think whether G_CF_SPOILED should also be cleared there then?

This revision is now accepted and ready to land.Sep 20 2017, 9:20 PM
This revision was automatically updated to reflect the committed changes.