Bug 1471405
Summary: | glibc: Define O_TMPFILE macro | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Florian Weimer <fweimer> |
Component: | glibc | Assignee: | DJ Delorie <dj> |
Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.5 | CC: | ashankar, bugproxy, cmaiolin, codonell, fweimer, hannsj_uhl, mnewsome, pfrankli, skolosov |
Target Milestone: | rc | Keywords: | Patch |
Target Release: | 7.6 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glibc-2.17-237.el7 | Doc Type: | Enhancement |
Doc Text: |
The O_TMPFILE macro is now present in glibc headers.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 09:36:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1428677 | ||
Bug Blocks: | 1513404, 1565233 |
Description
Florian Weimer
2017-07-15 16:49:26 UTC
Hello Red Hat / Florian, quick question ... ... with the related kernel support now available in RHEL7.5 (see LTC bug 152133 - RH1428677- [7.5 FEAT] O_TMPFILE Support for RHEL 7 ...) I would think that this bugzilla can now be processed (but maybe first for RHEL7.6 ..) ... ... correct ...? Please confirm or advise ... Thanks for your support. (In reply to Hanns-Joachim Uhl from comment #3) > Hello Red Hat / Florian, > quick question ... > ... with the related kernel support now available in RHEL7.5 > (see LTC bug 152133 - RH1428677- [7.5 FEAT] O_TMPFILE Support for RHEL 7 ...) > I would think that this bugzilla can now be processed > (but maybe first for RHEL7.6 ..) ... > ... correct ...? > Please confirm or advise ... > Thanks for your support. Yes, in RHEL 7.6 we can now consider adding O_TMPFILE. This bug will be reviewed as we enter the RHEL 7.6 planning. ------- Comment From oehmes.com 2018-02-08 11:19 EDT------- i am confused, the change was original accepted in 7.5, why is it now moving to 7.6 ? (In reply to IBM Bug Proxy from comment #5) > ------- Comment From oehmes.com 2018-02-08 11:19 EDT------- > i am confused, the change was original accepted in 7.5, why is it now moving > to 7.6 ? The work in glibc to define O_TMPFILE was never accepted in rhel-7.5. The work will be reviewed again as part of our planning for rhel-7.6. My apologies if you had any other indicator that this would be delivered in glibc in rhel-7.5. If you had such indicators, then please tell me about them, and I will review them. There may be some confusion about the kernel side of this fix versus the glibc side of the fix. The kernel fix is tracked separately here: https://bugzilla.redhat.com/show_bug.cgi?id=1428677, and must be delivered first before any userspace constants can be added to enable the functionality. (In reply to Carlos O'Donell from comment #6) > The kernel fix is tracked separately here: > https://bugzilla.redhat.com/show_bug.cgi?id=1428677, and must be delivered > first before any userspace constants can be added to enable the > functionality. It's not entirely true that the kernel fix has to come first, but generally speaking we like to have the kernel functionality land first, then the userspace enablement. This avoids cases where applications look for the constants in configure scripts and then unconditionally enable the feature without runtime detection. Such applications would be immediately broken if we signaled via the header constant that the feature was ready for use. By staging the enablement a bit we ensure the users are likely running the latest released kernel. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:3092 |