Project

General

Profile

Actions
Copy link

Backport #50391

closed

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

Added by Backport Bot about 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Jeff Layton
Target version:
-
Release:
pacific
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Related issues 1 (0 open — 1 closed)

Copied from CephFS - Bug #50305: MDS doesn't set fscrypt flag on new inodes with crypto context in xattr bufferResolvedJeff Layton

Actions
Actions
Copy link
 #1

Updated by Backport Bot about 3 years ago

  • Copied from Bug #50305: MDS doesn't set fscrypt flag on new inodes with crypto context in xattr buffer added
Actions
Copy link
 #2

Updated by Patrick Donnelly about 3 years ago

  • Status changed from New to Need More Info
  • Assignee set to Jeff Layton

No longer certain we want to backport this -- Jeff is considering another approach.

Actions
Copy link
 #3

Updated by Jeff Layton almost 3 years ago

  • Status changed from Need More Info to Rejected

Yeah. This is some basic infrastructure that we merged for fscrypt support, but it's going to require more changes before this is usable. I'm going to reject this for now, and we can reopen this or a new bug once we have a more complete solution for fscrypt.

Actions
Copy link

Also available in: Atom PDF