Bug 1866940 - libcephfs uses static dirent for readdir which is not thread-safe
Summary: libcephfs uses static dirent for readdir which is not thread-safe
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 4.1
Hardware: All
OS: All
urgent
urgent
Target Milestone: z2
: 4.1
Assignee: Patrick Donnelly
QA Contact: Hemanth Kumar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-06 21:47 UTC by Patrick Donnelly
Modified: 2020-09-30 17:27 UTC (History)
4 users (show)

Fixed In Version: ceph-14.2.8-94.el8cp, ceph-14.2.8-94.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-30 17:26:56 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 46856 0 None None None 2020-08-07 23:24:01 UTC
Red Hat Product Errata RHBA-2020:4144 0 None None None 2020-09-30 17:27:30 UTC

Description Patrick Donnelly 2020-08-06 21:47:25 UTC
Description of problem:

See: https://tracker.ceph.com/issues/46832

This issue can be reproduced by running the tasks/volumes task in the upstream teuthology suite and grepping the mgr logs for a "Traceback" looking like what is in the above issue description. The specific test may _not_ fail because another purge thread picks up the work.

This is urgent because it's conceivable but extremely unlikely that two threads writing to the same dirent may construct an invalid file name. In particular, the volumes plugin purge threads may accidentally recursively remove a file path containing "../" which would cause the threads to delete parent directories above the subvolume to be deleted.

Comment 10 errata-xmlrpc 2020-09-30 17:26:56 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 (Red Hat Ceph Storage 4.1 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/RHBA-2020:4144


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