Bug 1797915
| Summary: | [abrt] [faf] g_ascii_strtoll() for "10" failed with errno=11 (Resource temporarily unavailable) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> | ||||||
| Component: | NetworkManager | Assignee: | Thomas Haller <thaller> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7.8 | CC: | acardace, atragler, bgalvani, lrintel, rkhan, sukulkar, thaller, till | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://faf.lab.eng.brq.redhat.com/faf/reports/bthash/174421a9a5c74c353f2b14c55e973df4785eae18/ | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | NetworkManager-1.18.6-2.el7 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-09-29 20:30:25 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Vladimir Benes
2020-02-04 08:28:28 UTC
Created attachment 1662161 [details] backtrace from https://faf.lab.eng.brq.redhat.com/faf/reports/15962/ it's unclear how this assertion failure can happen. (also, it can only happen in test-builds (--with-more-asserts). In production builds -- i.e. official RPMs in brew -- this cannot happen because the assertion is disabled). I pushed https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/90c5d1d99cea8a8a8edafb0c02f421979cf56b37 which might help finding the issue if it happens again. Also, this might be very well some form of memory corruption, so with the provided information it's unclear how exactly... Let's wait for it to happen again. It's actually happened 5 times already. Added new debug messages: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf6940665dac3f5c62782acd590d5fca7e2cd76e here again: 01 Mar 2020 and again today: 04 Mar 2020 is there anything more visible from the new logs build? (In reply to Vladimir Benes from comment #8) > is there anything more visible from the new logs build? No, unfortunately the FAF report only includes a tar.gz for the first crash, which is NetworkManager-1.23.1-24939.9a971849b5.el7-ccpp-2020-02-03-19-29-56-28501.tar.gz I can't find backtraces for later ones. Do you know if it's possible to 'forget' this report, so that a new one will be created with the new backtrace and tarball? (In reply to Beniamino Galvani from comment #9) > (In reply to Vladimir Benes from comment #8) > > is there anything more visible from the new logs build? > > No, unfortunately the FAF report only includes a tar.gz for the first crash, > which is > > > NetworkManager-1.23.1-24939.9a971849b5.el7-ccpp-2020-02-03-19-29-56-28501. > tar.gz > > I can't find backtraces for later ones. Do you know if it's possible to > 'forget' this report, so that a new one will be created with the new > backtrace and tarball? we should see more here: http://faf.lab.eng.brq.redhat.com/faf/reports/16800/ we have one more from today: https://faf.lab.eng.brq.redhat.com/faf/reports/16810/ at https://beaker.engineering.redhat.com/recipes/8060079#task108127080 : 2020-03-25, build 1.23.2-25251.fbb65de32e.el7 > [ 4622.324332] gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com restraintd[1616]: (process:11071): libnm-ERROR **: 11:41:12.860: unexpected assertion failure: could parse "10.16.122.90" as 10.16.122.90, but not accepted by legacy parser: invalid token '10' at https://beaker.engineering.redhat.com/recipes/8067937#task108212265 2020-03-27, 1.23.2-25274.54aaf240d2.el7 [ 2302.670735] gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com restraintd[1618]: (process:22999): libnm-ERROR **: 11:03:00.967: unexpected assertion failure: could parse "10.16.122.90" as 10.16.122.90, but not accepted by legacy parser: invalid token '10' at https://beaker.engineering.redhat.com/recipes/8070652#task108243276 2020-03-28, 1.23.2-25275.c84a4579b2.el7 [ 2399.713680] gsm-r5s9-01.wlan.rhts.eng.bos.redhat.com restraintd[1656]: (process:15978): libnm-ERROR **: 03:01:17.455: unexpected assertion failure: could parse "10.16.122.97" as 10.16.122.97, but not accepted by legacy parser: invalid token '10' Still no idea. WIP for workaround here: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/456 via http://faf.lab.eng.brq.redhat.com/faf/reports/16845/ , https://beaker.engineering.redhat.com/recipes/8080594#task108346166 we get (process:13347): libnm-ERROR **: 12:35:44.434: g_ascii_strtoll() for "10" failed with errno=11 (Resource temporarily unavailable) and v=10 workaround merged to master: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/d342fa267d59cd317cc3cc798824c70b1158ff61 nm-1-22: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/85811e67ddcdeb47a88aca177c75436f75d5e79e Let's see if that avoids the crash. Then we should see whether to backport it further and/or to RHEL, and how to fix it in glib. Created attachment 1684971 [details] dist-git for "glib2-2.56.1-6" to reproduce issue Seems the crashes only happened on RHEL-7, and the workaround to NetworkManager worked. To further identify where the issue comes from, let's test with a modified glib2 package (see attached dist-git patch). @Vladimir, please run our glib2 tests with scratch-build https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28362505, if that causes new crashes, we can see where the issue is. not visible anymore 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 (Moderate: NetworkManager security and 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/RHSA-2020:4003 |