Project

General

Profile

Bug #56553

client: do not uninline data for read

Added by Xiubo Li 7 months ago. Updated 5 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
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:
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

Copied to CephFS - Backport #57571: pacific: client: do not uninline data for read In Progress
Copied to CephFS - Backport #57572: quincy: client: do not uninline data for read In Progress

History

#1 Updated by Xiubo Li 7 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 47090

#2 Updated by Venky Shankar 5 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to pacific,quincy

#3 Updated by Backport Bot 5 months ago

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

#4 Updated by Backport Bot 5 months ago

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

#5 Updated by Backport Bot 5 months ago

  • Tags set to backport_processed

Also available in: Atom PDF