Project

General

Profile

Actions
Copy link

Bug #41252

closed

rgw_file: readdir: do not construct markers w/leading '/'

Added by Matt Benjamin over 4 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Matt Benjamin
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus, mimic, luminous
Regression:
Yes
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
29670
Crash signature (v1):
Crash signature (v2):

Description

This case arises when listing the top directory of a bucket, and,
with proper continued enumeration, would generate a non-terminating
loop if a directory contained names which sort lexically before '/'.

This is a regression due to new enumeration logic in nfs-ganesha 2.7.x.

Related issues 3 (0 open — 3 closed)

Copied to rgw - Backport #41342: mimic: rgw_file: readdir: do not construct markers w/leading '/'ResolvedNathan CutlerActions
Copied to rgw - Backport #41343: luminous: rgw_file: readdir: do not construct markers w/leading '/'RejectedActions
Copied to rgw - Backport #41446: nautilus: rgw_file: readdir: do not construct markers w/leading '/'ResolvedNathan CutlerActions
Actions
Copy link
 #1

Updated by Matt Benjamin over 4 years ago

  • Status changed from In Progress to Fix Under Review
Actions
Copy link
 #2

Updated by Matt Benjamin over 4 years ago

  • Pull request ID set to 29670
Actions
Copy link
 #3

Updated by Matt Benjamin over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #4

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41342: mimic: rgw_file: readdir: do not construct markers w/leading '/' added
Actions
Copy link
 #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41343: luminous: rgw_file: readdir: do not construct markers w/leading '/' added
Actions
Copy link
 #6

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41446: nautilus: rgw_file: readdir: do not construct markers w/leading '/' added
Actions
Copy link
 #7

Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF