Project

General

Profile

Bug #50060

client: access(path, X_OK) on non-executable file as root always succeeds

Added by Patrick Donnelly almost 3 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
High
Category:
Correctness/Safety
Target version:
% Done:

0%

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

Description

See "[ceph-users] ceph-fuse false passed X_OK check".

Check works for non-root users.


Related issues

Copied to CephFS - Backport #50626: octopus: client: access(path, X_OK) on non-executable file as root always succeeds Resolved
Copied to CephFS - Backport #50627: pacific: client: access(path, X_OK) on non-executable file as root always succeeds Resolved
Copied to CephFS - Backport #50628: nautilus: client: access(path, X_OK) on non-executable file as root always succeeds Resolved

History

#1 Updated by Patrick Donnelly almost 3 years ago

  • Status changed from New to Triaged
  • Assignee set to Kotresh Hiremath Ravishankar

#2 Updated by Kotresh Hiremath Ravishankar almost 3 years ago

  • Pull request ID set to 40882

#3 Updated by Kotresh Hiremath Ravishankar almost 3 years ago

  • Status changed from Triaged to Fix Under Review

#4 Updated by Patrick Donnelly almost 3 years ago

  • Status changed from Fix Under Review to Pending Backport

#5 Updated by Backport Bot almost 3 years ago

  • Copied to Backport #50626: octopus: client: access(path, X_OK) on non-executable file as root always succeeds added

#6 Updated by Backport Bot almost 3 years ago

  • Copied to Backport #50627: pacific: client: access(path, X_OK) on non-executable file as root always succeeds added

#7 Updated by Backport Bot almost 3 years ago

  • Copied to Backport #50628: nautilus: client: access(path, X_OK) on non-executable file as root always succeeds added

#8 Updated by Loïc Dachary about 2 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".

Also available in: Atom PDF