Description of problem:
Incorrect response from lvmetad is not handled correctly and causes segfault.
Parsing procedure returns NULL pointer which is dereferenced later:
<pre>
static inline const char *daemon_reply_str(daemon_reply r, const char *path, const ...|char *def) {
return dm_config_find_str(r.cft->root, path, def);
}
</pre>
Here the r.cft is 0x0
Version-Release number of selected component (if applicable):
lvm2-2.02.97-0.151
How reproducible:
low reproducibility of original lvmetad bug.
but this would crash 100% of time when wrong data are received.
Steps to Reproduce:
Bug 845259 in lvmetad would crash client.
Actual results:
segfault
Expected results:
error message or retry?
Additional info:
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.
http://rhn.redhat.com/errata/RHBA-2013-0501.html
Description of problem: Incorrect response from lvmetad is not handled correctly and causes segfault. Parsing procedure returns NULL pointer which is dereferenced later: <pre> static inline const char *daemon_reply_str(daemon_reply r, const char *path, const ...|char *def) { return dm_config_find_str(r.cft->root, path, def); } </pre> Here the r.cft is 0x0 Version-Release number of selected component (if applicable): lvm2-2.02.97-0.151 How reproducible: low reproducibility of original lvmetad bug. but this would crash 100% of time when wrong data are received. Steps to Reproduce: Bug 845259 in lvmetad would crash client. Actual results: segfault Expected results: error message or retry? Additional info: