Project

General

Profile

Actions

Bug #50090

closed

client: only check pool permissions for regular files

Added by Xiubo Li about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Performance/Resource Usage
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
pacific,octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
fs
Component(FS):
Client
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

There is no need to do a check_pool_perm() on anything that isn't
a regular file, as the MDS is what handles talking to the OSD in
those cases. Just return 0 if it's not a regular file.


Related issues 3 (0 open3 closed)

Copied to CephFS - Backport #50179: nautilus: client: only check pool permissions for regular filesResolvedNathan CutlerActions
Copied to CephFS - Backport #50180: pacific: client: only check pool permissions for regular filesResolvedsinguliere _Actions
Copied to CephFS - Backport #50181: octopus: client: only check pool permissions for regular filesResolvedNathan CutlerActions
Actions #1

Updated by Xiubo Li about 3 years ago

  • Pull request ID set to 40460
Actions #2

Updated by Patrick Donnelly about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version set to v17.0.0
  • Source set to Development
  • Backport set to pacific,octopus,nautilus
  • Component(FS) Client added
  • Component(FS) deleted (libcephfs)
Actions #3

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50179: nautilus: client: only check pool permissions for regular files added
Actions #4

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50180: pacific: client: only check pool permissions for regular files added
Actions #5

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50181: octopus: client: only check pool permissions for regular files added
Actions #6

Updated by Loïc Dachary almost 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

Also available in: Atom PDF