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 1099511 - [PATCH] rpmdb often gets corrupted upon concurrent access due to a race in CDB
Summary: [PATCH] rpmdb often gets corrupted upon concurrent access due to a race in CDB
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: db4
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Staněk
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1112653
TreeView+ depends on / blocked
 
Reported: 2014-05-20 13:37 UTC by Lubomir Rintel
Modified: 2017-10-06 17:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1099509
: 1112653 (view as bug list)
Environment:
Last Closed: 2015-10-14 06:32:17 UTC
Target Upstream Version:
Embargoed:
mleitner: needinfo-


Attachments (Terms of Use)
Fix for bdb issue #3514381; el6/db4 (2.67 KB, patch)
2014-05-20 13:37 UTC, Lubomir Rintel
no flags Details | Diff

Description Lubomir Rintel 2014-05-20 13:37:45 UTC
Created attachment 897576 [details]
Fix for bdb issue #3514381; el6/db4

Cloning the bug for el6.
The patch is a bit different, the older version only contains the reader/writer table issue.

+++ This bug was initially created as a clone of Bug #1099509 +++

Description of problem:

Our continuous integration often encounters a situation when rpmdb gets corrupted while a rpmdb reader meets with a package installation. We've tracked down the issue to a race condition in CDB and upstream had now kindly provided a fix.

Upstream bug report: https://community.oracle.com/thread/3514381

Test cases (slow one, that reproduces the issue with RPM, and a minimal one for db4) are here: http://v3.sk/~lkundrak/bdb-crash/

Attaching the fix.

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

libdb-5.3.21-17.el7.x86_64

Comment 12 Jan Staněk 2014-07-08 09:01:45 UTC
Hi Lubomir,
the provided fix seems nonworking - the tests still fails even with db4 with provided patch applied.

Test run:
$ make test
sh test.sh
Tue Jul  8 09:52:20 CEST 2014
test.sh: line 9: 17651 Segmentation fault      (core dumped) ./reader
Reader died
test.sh: line 12: 22785 Terminated              ( while ./writer; do
    :;
done; echo 'Writer died' )
Tue Jul  8 10:29:34 CEST 2014

Backtrace:
$ gdb ./reader core.17651
Program terminated with signal 11, Segmentation fault.
#0  0x0000003203678674 in _int_free () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.147.el6.x86_64
(gdb) bt
#0  0x0000003203678674 in _int_free () from /lib64/libc.so.6
#1  0x00000036cd902dd0 in __env_region_detach (env=0xac66b0, infop=0xac6b78, destroy=<value optimized out>)
    at ../../env/env_region.c:1099
#2  0x00000036cd8b4217 in __mutex_env_refresh (env=0xac66b0) at ../../mutex/mut_region.c:275
#3  0x00000036cd90023b in __env_refresh (dbenv=0xac6010, orig_flags=0, rep_check=0)
    at ../../env/env_open.c:966
#4  0x00000036cd900524 in __env_close (dbenv=0xac6010, rep_check=0) at ../../env/env_open.c:736
#5  0x00000036cd90073a in __env_close_pp (dbenv=0xac6010, flags=<value optimized out>)
    at ../../env/env_open.c:695
#6  0x0000000000400b58 in env_close () at test.c:71
#7  0x0000000000400ea8 in main () at test.c:152
(gdb) quit

Comment 22 RHEL Program Management 2014-07-28 12:45:45 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

Comment 24 Honza Horak 2014-07-28 12:53:37 UTC
Let's keep this bug opened since there indeed is an issue, we only do not have a patch yet. Also recovering the need info for the reporter as per comment #12.

Comment 27 Honza Horak 2015-10-14 06:32:17 UTC
Since there has been no further input given and we're not able to fix the bug with the current information provided, closing the bug. Please, re-open in case there is some additional information that we can use to fix the issue.


Note You need to log in before you can comment on or make changes to this bug.