Project

General

Profile

Actions

Feature #44279

open

client: provide asok commands to getattr an inode with desired caps

Added by Patrick Donnelly about 4 years ago. Updated about 1 year ago.

Status:
Fix Under Review
Priority:
Normal
Assignee:
Category:
Introspection/Control
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Client, qa-suite
Labels (FS):
qa
Pull request ID:

Description

Idea is to avoid using UNIX commands or libcephfs calls to implicitly acquire the caps we want. Instead, write a command that explicitly tries to acquire caps for an inode.

This is a first step to creating a test suite for cap acquisition/revoke behavior with the MDS.


Related issues 1 (1 open0 closed)

Related to CephFS - Feature #45021: client: new asok commands for diagnosing cap handling issuesIn ProgressVenky Shankar

Actions
Actions #1

Updated by Greg Farnum about 4 years ago

We may also just want to bring the SynClient or do something directly with libcephfs to grab exact sequences instead of going through the ceph-fuse asok.

Actions #2

Updated by Patrick Donnelly almost 4 years ago

  • Assignee set to Kotresh Hiremath Ravishankar
Actions #3

Updated by Jeff Layton almost 4 years ago

Do we need an asok interface for this? If you're planning to write testcases that link in libcephfs directly, then you can just add new libcephfs calls that do what you want, and write testcases that just call them.

The main reason to add something like asok interface would be if you want to be able to issue these sorts of requests in conjunction with (e.g.) a FUSE mount or ganesha export. Are you planning to do that?

Actions #4

Updated by Patrick Donnelly almost 4 years ago

Jeff Layton wrote:

Do we need an asok interface for this? If you're planning to write testcases that link in libcephfs directly, then you can just add new libcephfs calls that do what you want, and write testcases that just call them.

The main reason to add something like asok interface would be if you want to be able to issue these sorts of requests in conjunction with (e.g.) a FUSE mount or ganesha export. Are you planning to do that?

The eventual goal is to test the expected behavior of two clients issuing getattr requests. Yes, we could simulate with UNIX syscalls like `mkdir' but that relies on second order effects -- what caps the `mkdir` operation will try to fetch (which may touch many inodes in the path lookup). It's better to directly test the behavior you're trying to confirm without any extraneous operations.

Actions #5

Updated by Kotresh Hiremath Ravishankar almost 4 years ago

  • Status changed from New to In Progress
Actions #6

Updated by Kotresh Hiremath Ravishankar almost 4 years ago

  • Pull request ID set to 35992
Actions #7

Updated by Patrick Donnelly almost 4 years ago

  • Status changed from In Progress to Fix Under Review
Actions #8

Updated by Patrick Donnelly about 3 years ago

  • Target version changed from v16.0.0 to v17.0.0
Actions #9

Updated by Patrick Donnelly almost 2 years ago

  • Target version deleted (v17.0.0)
Actions #10

Updated by Venky Shankar about 1 year ago

  • Related to Feature #45021: client: new asok commands for diagnosing cap handling issues added
Actions #11

Updated by Venky Shankar about 1 year ago

  • Category set to Introspection/Control
  • Assignee changed from Kotresh Hiremath Ravishankar to Venky Shankar
  • Target version set to v19.0.0
Actions

Also available in: Atom PDF