diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2023-03-07 14:45:06 +0100 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2023-03-07 15:29:54 +0100 |
| commit | cd14d3fcc0e03136d0cea1ab1a9edff3b8b9dbeb (patch) | |
| tree | 429234aa9883898b15a445435cdbce55f833e0d4 /WHATS_NEW | |
| parent | c8f2125b85afe043af1b2e887a80f882b8d8d7c7 (diff) | |
| download | lvm2-cd14d3fcc0e03136d0cea1ab1a9edff3b8b9dbeb.tar.gz | |
toollib: fix segfault if using -S|--select with log/report_command_log=1 setting
When we are using -S|--select for non-reporting tools while using command log
reporting (log/report_command_log=1 setting), we need to create an internal
processing handle to handle the selection itself. In this case, the internal
processing handle to execute the selection (to process the -S|--select) has
a parent handle (that is processing the actual non-reporting command).
When this parent handle exists, we can't destroy the command log report
in destroy_processing_handle as there's still the parent processing to
finish. The parent processing may still generate logs which need to be
reported in the command log report. If the command log report was
destroyed prematurely together with destroying the internal processing
handle for -S|--select, then any subsequent log request from processing
the actual command (and hence an attermpt to access the command log report)
ended up with a segfault.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=2175220
Diffstat (limited to 'WHATS_NEW')
| -rw-r--r-- | WHATS_NEW | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1,5 +1,6 @@ version 2.03.20 - ==================================== + Fix segfault if using -S|--select with log/report_command_log=1 setting. Configure now fails when requested lvmlockd dependencies are missing. Add some configure Gentoo enhancements for static builds. |