Project

General

Profile

Actions
Copy link

Bug #56553

closed

client: do not uninline data for read

Added by Xiubo Li almost 2 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Xiubo Li
Category:
-
Target version:
-
% Done:

0%

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

Description

We don't even ask for and to be sure that we have been granted the Fw caps when reading, we shouldn't write contents to Rados.

Related issues 2 (0 open — 2 closed)

Copied to CephFS - Backport #57571: pacific: client: do not uninline data for readResolvedXiubo LiActions
Copied to CephFS - Backport #57572: quincy: client: do not uninline data for readResolvedXiubo LiActions
Actions
Copy link
 #1

Updated by Xiubo Li almost 2 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 47090
Actions
Copy link
 #2

Updated by Venky Shankar over 1 year ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to pacific,quincy
Actions
Copy link
 #3

Updated by Backport Bot over 1 year ago

  • Copied to Backport #57571: pacific: client: do not uninline data for read added
Actions
Copy link
 #4

Updated by Backport Bot over 1 year ago

  • Copied to Backport #57572: quincy: client: do not uninline data for read added
Actions
Copy link
 #5

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions
Copy link
 #6

Updated by Xiubo Li about 1 year ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF