Bug 1477284 - segmentation fault when running thin_delta with wrong -- option
segmentation fault when running thin_delta with wrong -- option
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-persistent-data (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Joe Thornber
Jakub Krysl
Depends On:
  Show dependency treegraph
Reported: 2017-08-01 11:37 EDT by Jakub Krysl
Modified: 2018-04-10 09:18 EDT (History)
6 users (show)

See Also:
Fixed In Version: device-mapper-persistent-data-0.7.2-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-10 09:17:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0776 None None None 2018-04-10 09:18 EDT

  None (edit)
Description Jakub Krysl 2017-08-01 11:37:13 EDT
Description of problem:
If thin_delta is ran with wrong -- option (eg. not --thin1, --help...), it produces segmentation fault.

[28278.820618] thin_delta[8678]: segfault at a ip 00007f81bdc11e4c sp 00007ffe9dd7e808 error 4 in libc-2.17.so[7f81bdb8b000+1b8000]

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

How reproducible:

Steps to Reproduce:
1.thin_delta --whatever_wrong

Actual results:
Segmentation fault (core dumped)

Expected results:
Unknown option

Additional info:
Comment 2 Joe Thornber 2017-09-15 07:31:59 EDT
Fixed with this patch:


New release to follow in the next few days.
Comment 4 Jakub Krysl 2017-09-22 07:59:40 EDT
device-mapper-persistent-data-0.7.2-1.el7 returns message with 'unrecognized option' instead of segmentation fault, retcode is 1.
Comment 7 errata-xmlrpc 2018-04-10 09:17:29 EDT
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.


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