Project

General

Profile

Actions
Copy link

Bug #50305

closed

MDS doesn't set fscrypt flag on new inodes with crypto context in xattr buffer

Added by Jeff Layton about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jeff Layton
Category:
-
Target version:
Ceph - v17.0.0
% Done:

0%

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

Description

The new fscrypt context handling code will set the "fscrypt" flag when the encryption.ctx xattr is set explicitly, but it does not set it on new inodes that have a crypto context in the xattr blob from the client. Fix it to look for the encryption.ctx xattr on new inodes and set the flag appropriately.

Related issues 1 (0 open — 1 closed)

Copied to CephFS - Backport #50391: pacific: MDS doesn't set fscrypt flag on new inodes with crypto context in xattr bufferRejectedJeff LaytonActions
Actions
Copy link
 #1

Updated by Patrick Donnelly about 3 years ago

  • Status changed from New to Pending Backport
  • Target version set to v17.0.0
  • Source set to Development
  • Backport set to pacific
  • Pull request ID set to 40828
  • Component(FS) MDS added
Actions
Copy link
 #2

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50391: pacific: MDS doesn't set fscrypt flag on new inodes with crypto context in xattr buffer added
Actions
Copy link
 #3

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