Actions
Bug #52921
openkclient: the read path is buggy when reading the inline data
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
Currently the kclient only partially support the inline data feature, that is the write path will always uninline data and the read path will always assume the inline data size is less than or equal to the PAGE_SIZE, but the fuse client allow users to change the default max inline data size, which is 4K, for example in case the max inline data size is increased to 8K, while the kernel PAGE_SIZE is still 4K, the kclient will always use one PAGE to store the inline data.
Since the inline data feature will be removed from kclient, more detail please see [1], this bug won't be fixed, just record it here.
Updated by Xiubo Li over 2 years ago
- Related to Fix #52916: mds,client: formally remove inline data support added
Actions