Project

General

Profile

Backport #50391

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

Added by Backport Bot 20 days ago. Updated 6 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
-
Release:
pacific
Crash signature (v1):
Crash signature (v2):

Related issues

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

History

#1 Updated by Backport Bot 20 days ago

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

#2 Updated by Patrick Donnelly 17 days 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.

#3 Updated by Jeff Layton 6 days 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.

Also available in: Atom PDF