RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1824802 - Rare assertion failure about waiters.
Summary: Rare assertion failure about waiters.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Sweet Tea Dorminy
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-16 13:16 UTC by Sweet Tea Dorminy
Modified: 2021-09-06 15:18 UTC (History)
3 users (show)

Fixed In Version: 6.2.3.91
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:01:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4551 0 None None None 2020-11-04 02:01:57 UTC

Description Sweet Tea Dorminy 2020-04-16 13:16:23 UTC 
Description of problem:
In certain rare circumstances in either async mode, there can be an assertion failure from the VDO recovery journal from it attempting to double-enqueue a block for writing. This requires IO to be in progress and the journal to have no space; the journal attempts never to get more than halfway full, so being full is unlikely.

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

How reproducible:
Exceedingly rare. Not observed except in unit tests.

Steps to Reproduce:
1. Unknown.

Actual results:
In userspace imitation in a unit test:
waitQueue.c:19: handleAssertionFailure: Assertion `(waiter->next_waiter == ((void *)0))' failed.
==7808== 
==7808== Process terminating with default action of signal 6 (SIGABRT): dumping core
==7808==    at 0x4B0957F: raise (in /usr/lib64/libc-2.28.so)
==7808==    by 0x4AF3894: abort (in /usr/lib64/libc-2.28.so)
==7808==    by 0x4AF3768: __assert_fail_base.cold.0 (in /usr/lib64/libc-2.28.so)
==7808==    by 0x4B01A25: __assert_fail (in /usr/lib64/libc-2.28.so)
==7808==    by 0x48BB74A: handleAssertionFailure (permassertLinuxUser.c:83)
==7808==    by 0x48B530C: assertionFailed (permassert.c:24)
==7808==    by 0x489F94D: enqueue_waiter (waitQueue.c:18)
==7808==    by 0x488B028: schedule_block_write (recoveryJournal.c:845)
==7808==    by 0x488B028: complete_write (recoveryJournal.c:1110)

The kernel assertion would look similar.

Expected results:
No assertion.

Additional info:
This bug was introduced in fixing 1657301
Comment 3 Filip Suba 2020-08-21 07:42:12 UTC 
Verified SanityOnly. Regression testing passed.
Comment 6 errata-xmlrpc 2020-11-04 02:01:47 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 (kmod-kvdo bug fix and enhancement 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:4551
Note You need to log in before you can comment on or make changes to this bug.