Bug 1727152 - glibc: Avoid nscd assertion failure during persistent db check
Summary: glibc: Avoid nscd assertion failure during persistent db check
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1684559
TreeView+ depends on / blocked
 
Reported: 2019-07-04 17:29 UTC by Florian Weimer
Modified: 2023-07-18 14:30 UTC (History)
7 users (show)

Fixed In Version: glibc-2.28-70.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:29:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-24082 0 None None None 2021-09-17 12:23:56 UTC
Red Hat Product Errata RHSA-2019:3513 0 None None None 2019-11-05 21:29:23 UTC

Description Florian Weimer 2019-07-04 17:29:55 UTC 
We need to backport this upstream patch:

commit 61595e3d36ded374f97961503e843a314b0203c2
Author: Andreas Schwab <schwab>
Date:   Tue May 15 14:42:37 2018 +0200

    nscd: avoid assertion failure during persistent db check
    
    nscd should not abort when it finds inconsistencies in the persistent db.
Comment 7 Sergey Kolosov 2019-09-26 18:26:39 UTC 
Verified by corrupting a record of /var/db/passwd file:

on glibc-2.28-69.el8 nscd crashes:
 nscd: connections.c:307: check_use: Assertion `len >= 2' failed.
Aborted (core dumped)

on glibc-2.28-70.el8 nscd reports about invalid DB and continue works:
 invalid persistent database file "/var/db/nscd/passwd": verification failed
Comment 11 errata-xmlrpc 2019-11-05 21:29:05 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, 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-2019:3513
Note You need to log in before you can comment on or make changes to this bug.