Project

General

Profile

Bug #42107

client: no method to handle SEEK_HOLE and SEEK_DATA in lseek

Added by shen hang 12 months ago. Updated 3 months ago.

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

0%

Source:
Community (dev)
Tags:
Backport:
nautilus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
ceph-fuse
Labels (FS):
Pull request ID:
Crash signature:

Description

There is no method to handle SEEK_HOLE and SEEK_DATA in lseek in ceph-fuse


Related issues

Related to fs - Bug #42602: client: missing const SEEK_DATA and SEEK_HOLE on ALPINE LINUX Resolved
Copied to fs - Backport #42121: nautilus: client: no method to handle SEEK_HOLE and SEEK_DATA in lseek Resolved
Copied to fs - Backport #42122: mimic: client: no method to handle SEEK_HOLE and SEEK_DATA in lseek Resolved
Copied to fs - Backport #42123: luminous: client: no method to handle SEEK_HOLE and SEEK_DATA in lseek Resolved

History

#1 Updated by Patrick Donnelly 12 months ago

  • Subject changed from client:no method to handle SEEK_HOLE and SEEK_DATA in lseek to client: no method to handle SEEK_HOLE and SEEK_DATA in lseek
  • Status changed from New to Pending Backport
  • Assignee set to shen hang
  • Target version set to v15.0.0
  • Start date deleted (10/01/2019)
  • Source set to Community (dev)
  • Backport set to nautilus,mimic,luminous

#2 Updated by Nathan Cutler 12 months ago

  • Copied to Backport #42121: nautilus: client: no method to handle SEEK_HOLE and SEEK_DATA in lseek added

#3 Updated by Nathan Cutler 12 months ago

  • Copied to Backport #42122: mimic: client: no method to handle SEEK_HOLE and SEEK_DATA in lseek added

#4 Updated by Nathan Cutler 12 months ago

  • Copied to Backport #42123: luminous: client: no method to handle SEEK_HOLE and SEEK_DATA in lseek added

#5 Updated by Patrick Donnelly 11 months ago

  • Related to Bug #42602: client: missing const SEEK_DATA and SEEK_HOLE on ALPINE LINUX added

#6 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF