Bug 1551068

Summary: Radius service crashes with "Bad talloc magic value - unknown value" when using module sql rlm_sql [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: freeradiusAssignee: Nikolai Kondrashov <nikolai.kondrashov>
Status: CLOSED ERRATA QA Contact: Jaroslav Aster <jaster>
Severity: high Docs Contact: Ioanna Gkioka <igkioka>
Priority: urgent    
Version: 7.4CC: bwelterl, fkrska, igkioka, mdshaikh, nikolai.kondrashov, nkinder, pkis, toneata
Target Milestone: rcKeywords: Patch, Reproducer, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, when using the rlm_sql module for accounting data, memory space allocated with the talloc system was freed twice. As a consequence, the FreeRADIUS server terminated unexpectedly with the following error message: "Bad talloc magic value - unknown value" This update removes the repeated call of the talloc_free() function. As a result, FreeRADIUS no longer crashes in the described scenario.
Story Points: ---
Clone Of: 1540580 Environment:
Last Closed: 2018-04-17 16:38:31 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: 1540580    
Bug Blocks:    

Description Oneata Mircea Teodor 2018-03-02 16:58:10 UTC
This bug has been copied from bug #1540580 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 8 Patrik Kis 2018-04-03 13:22:21 UTC
Please note that the next batch update for 7.4.eus is in less than two weeks. The advisory has to be ready before 2018-04-16 and QE can not start working on it before it is switched to ON_QE.
Please proceed with this request asap otherwise the deadline for this batch update may be missed. Due to the current high workload in QE team (other 7.5.z and 7.4.z advisories), we might have problems do delivery this in time.

Comment 14 errata-xmlrpc 2018-04-17 16:38:31 UTC
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:1153