Bug 2203909
| Summary: | client: possibly wild pointer read when reconnection to mds | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Venky Shankar <vshankar> |
| Component: | CephFS | Assignee: | Milind Changire <mchangir> |
| Status: | CLOSED ERRATA | QA Contact: | Hemanth Kumar <hyelloji> |
| Severity: | medium | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | akraj, ceph-eng-bugs, cephqe-warriors, gfarnum, mchangir, tserlin |
| Target Milestone: | --- | ||
| Target Release: | 5.3z4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.10-176.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.Client programs no longer crash after releasing memory
Previously, when releasing memory, the pointer access would be saved for future reference. This caused the programs to crash on the client-side.
With this fix, memory is allocated and `UserPerm` contents are copied to newly allocated memory instead of saving pointers for future reference, thereby preventing the programs from crashing.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-07-19 16:19:10 UTC | Type: | --- |
| 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: | |||
| Bug Blocks: | 2210690 | ||
|
Description
Venky Shankar
2023-05-15 14:56:18 UTC
Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity. 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 (Red Hat Ceph Storage 5.3 Bug Fix update), 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/RHBA-2023:4213 |