Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionThomas Jaskiewicz
2018-07-17 21:36:30 UTC
Description of problem:
In our nightly testing, we have seen an occasional general protection fault related to the UDS callback code path. Examining the source code, we have found a code path that was doing a bad thing and fixed it in bug 1533260. After doing the fix, we still see
a similar error happening in the same code path.
We believe there is a race condition in some synchronization code that came from the user mode implementation of UDS. Since this code is a reimplementation of the Linux kernel wait_for_condition mechanism, we have chosen to change the code to just use the existing kernel mechanism.
Version-Release number of selected component (if applicable):
How reproducible:
Very difficult. We have a test that does 1024 start/stop cycles of a single VDO device. Its purpose is to ensure that VDO instance numbers behave properly, but it was the first test to see the general protection fault (after 500 cycles). We run this test 2 or 3 times a night, and have seen this failure 5 times in the last six months.
SanityOnly is the reasonable test plan.
Steps to Reproduce:
1.
2.
3.
Actual results:
A general protection fault in the kvdo%u:callbsckW kernel process.
Expected results:
no general protection fault.
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.
https://access.redhat.com/errata/RHBA-2018:3094
Comment 6Thomas Jaskiewicz
2019-08-20 19:35:24 UTC
*** Bug 1693695 has been marked as a duplicate of this bug. ***