Bug 1761042 - tcmu-runner: fix possible crash when loging to file and the rsyslog buffer
Summary: tcmu-runner: fix possible crash when loging to file and the rsyslog buffer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: tcmu-runner
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: OCS 3.11.z Batch Update 6
Assignee: Prasanna Kumar Kalever
QA Contact: Vinayak Papnoi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-12 03:33 UTC by Xiubo Li
Modified: 2020-12-17 04:32 UTC (History)
7 users (show)

Fixed In Version: tcmu-runner-1.2.0-33.el7rhgs
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-17 04:31:42 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:5602 0 None None None 2020-12-17 04:32:12 UTC

Description Xiubo Li 2019-10-12 03:33:26 UTC
Description of problem:

Potentially if there has any error or failure happen when setting the logger file or rsyslog output stuff, there will be NULL pointer dereferencing when logging, which will crash the tcmu-runner daemon. 


Version-Release number of selected component (if applicable):


How reproducible:

Normally, this hasn't been ever seen in any test cases and only in theory in one case that the system run out of memories, or other potential cases which hasn't been seen yet. 


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Xiubo Li 2019-10-12 03:34:12 UTC
The fixing PR is: https://github.com/open-iscsi/tcmu-runner/pull/592

Comment 11 errata-xmlrpc 2020-12-17 04:31:42 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 (OpenShift Container Storage 3.11.z 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-2020:5602


Note You need to log in before you can comment on or make changes to this bug.