New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore early ZONE_ATTR_ values #1149
Conversation
With this patch, things are much happier in the zone and the
Retrieval of the ZONE_ATTR_FLAGS attribute is succeeding. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nobody outside the platform (illumos and any extras in a distro) consume these values, right? I don't think it is, but it's a question that should linger.
I can't imagine that they do, certainly not the higher-numbered ones which are related to the RSS capping. There's at least one project on there (glibc on illumos) which has the ZONE_FLAGS_ATTR value hard coded to 14, which is the value we're restoring it to. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So glibc is doing something stupid, huh? Why am I NOT surprised. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch on the truss(1) ones.
While testing the
s10
brand under the upcoming r151042 release, a service failed to come online:Some dtrace showed that the branded zone was requesting attribute number
14
:and, unfortunately, our attribute 14 is not what it once was:
it was renumbered as part of 4ece279
This restores the numbering of the early flags, so that they are what branded zones expect. It also re-synchronises the ones in the 20-29 range with the values in gate and moves the OmniOS/SmartOS-only ones to 30+