Bug 1581377
| Summary: | coredump with dfsgetinfo [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | samba | Assignee: | Andreas Schneider <asn> |
| Status: | CLOSED ERRATA | QA Contact: | Andrej Dzilský <adzilsky> |
| Severity: | urgent | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | urgent | ||
| Version: | 7.4 | CC: | adzilsky, amarecek, asn, gdeschner, heinrich.mislik, jarrpa, tscherf |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | samba-4.7.1-7.el7_5 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when a user connected to a distributed file system (DFS) share using the smbclient utility and executed the dfsgetinfo command, the smbd service handling the connection failed with a segmentation fault error. The bug has been fixed, and as a result, smbd no longer crashes when executing dfsgetinfo on a DFS share using smbclient.
|
Story Points: | --- |
| Clone Of: | 1570020 | Environment: | |
| Last Closed: | 2018-08-16 14:17:47 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: | 1570020 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-05-22 15:18:37 UTC
Doc Text ist not accurate. The crash happend in smbd an the server side regardless of the client. smbclient and rpcclient in samba-bug 13370 were just used to send dfs-requests to smbd. *** Bug 1590226 has been marked as a duplicate of this bug. *** Hello Andreas, 1. Is there any way to work around this bug? 2. If there is no work around, can we get a hotfix for the customer in support case #02118446? This issue is very critical for them. 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/RHBA-2018:2440 |